Beehiiv

The Corma and beehiiv integration keeps your newsletter workspace and its team seats in line with the people who publish. Built for creators, publishers and brands, beehiiv describes itself as the newsletter platform built for growth. Paid plans are priced by active subscribers, while team seats are capped on every plan except Enterprise, so who sits in the workspace matters for both budget and control.

Key takeaways

• The beehiiv pricing page lists team seats as 1 on Free, 2 on Lite, 10 on Pro and Unlimited on Enterprise, and the workspace Owner counts as a seat.
• Pending beehiiv invitations count toward the team seat limit until they are accepted or canceled.
• The beehiiv workspace roles are Owner, Admin, Member and Contributor, and beehiiv offers no view-only role for analytics.
• The beehiiv Enterprise plan supports SSO via SAML and OIDC, and SCIM provisioning to create, update and deactivate users.

Who controls a beehiiv workspace?

The Admin who created a publication becomes its Owner, and there can be only one Owner per publication or workspace. beehiiv's article on team roles explains that reassigning the Owner role inside the app does not change permissions: transferring ownership requires a support ticket. If the original Owner has left, beehiiv asks for confirmation from that Owner's email, and if that is not possible, support may require extra verification steps. Workspace-level access applies to every publication, including ones added later.

API access sits with the same people. Only workspace Owners and Admins can access API keys, and generating or accessing them triggers Stripe Identity Verification tied to the individual's beehiiv account. By default, a beehiiv API key can access every publication in the workspace, and only paid plans can limit a key to specific publications. API keys receive all granular OAuth scopes. beehiiv documents no expiry for API keys, and does not say whether a key keeps working after the Admin who created it is removed.

How Corma governs beehiiv

• Seats in the budget: the beehiiv plan, its team seats and its renewal date sit in SaaS subscription management.
• Owner and Admin roles under review: the roles that control API keys go into automated access reviews, so each holder is confirmed.
• Leavers with an ownership check: a leaver workflow in the IT Workflow Builder first checks whether the person is the Owner, so the transfer request reaches beehiiv support while their email can still confirm it, then asks an Admin to remove them from the Team page.
• API keys with an owner: beehiiv API keys are non-human identities, so each one needs a named owner and the regular rotation beehiiv's developer docs recommend.

Frequently asked questions

Does beehiiv support SSO and SCIM?

Yes, on Enterprise. Enterprise customers can configure SSO via SAML and OIDC with major identity providers, including Okta, Azure AD/Entra ID, Google Workspace, OneLogin and JumpCloud, with setup handled during onboarding. Enterprise accounts also support SCIM provisioning to create, update and deactivate users. Read how SCIM and SAML differ.

How does Corma connect to beehiiv?

beehiiv's developer docs list no endpoint to manage team members, so Corma's browser-based agents handle team steps in beehiiv's settings, in an isolated browser session with credentials taken from your password vault. See also how Corma covers email marketing tools such as Brevo.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know who still holds Owner or Admin rights in beehiiv? Book a Corma demo.