Bird

Bird

Govern Bird with Corma: workspace admin, developer and analyst roles, organization owners, SSO for every organization, SCIM 2.0 and workspace API keys.

The Corma and Bird integration keeps your Bird organization and its members in line with the teams who use them. Bird describes its platform as sending transactional notifications, marketing broadcasts and two-way replies across Email, SMS, WhatsApp, Apple Messages and Voice. The company announced that MessageBird is now Bird in February 2024, and its billing combines a prepaid balance, free tiers, pay-as-you-go usage and product plans.

Key takeaways

  • Bird workspace roles are admin, developer and analyst, while organization roles include owner, org_admin and billing_admin.
  • Removing someone from a Bird organization revokes all of their account access, and Bird blocks removing an organization's only owner.
  • Bird API keys belong to the workspace, so keys created by an employee keep working after that employee's user account is removed.
  • A Bird changelog entry dated September 18, 2026 says single sign-on is available to every organization, over SAML 2.0 or OIDC.

Why do Bird API keys survive departures?

Bird API keys are not personal. Bird's authentication guide states that when an employee leaves and their user account is removed, the keys they created keep working. A key can be given a fixed expiry date, while a key without one lives until revoked. Creating, editing and revoking keys requires the Admin or Developer workspace role, and an organization master key, available on request, is not revoked when its creator is removed.

Some actions stay with people. Changing workspace settings, managing members and issuing keys cannot be granted to API keys. Bird's audit log records team invitations, role changes and member removals, and its entries cannot be edited or deleted in the dashboard. Legacy MessageBird accounts remain separate from bird.com accounts, even with the same email address.

How Corma governs Bird

  • Owners and admins under review: owners, org_admins and workspace admins go into automated access reviews, and Bird itself says an organization should have more than one owner.
  • Leavers with a key check: a leaver workflow in the IT Workflow Builder asks a Bird admin to remove the person from the organization and to rotate the keys they had access to, as Bird's guide suggests.
  • API keys with an owner: workspace API keys and master keys are non-human identities, so each one needs a named owner and, where it fits, an expiry date.
  • Users outside SCIM: for SSO users who are not in a SCIM directory, Bird tells admins to review memberships and active sessions separately when someone leaves, so the leaver workflow keeps that step.

Frequently asked questions

Does Bird support SSO and SCIM?

Yes. Bird connects Okta, Microsoft Entra ID or Google Workspace over SAML 2.0 or OIDC, with an option to require SSO, although organization Owners keep access with their Bird password. SCIM 2.0 creates users, updates their roles and removes their access, with one directory per organization; it needs an active SSO connection and cannot adopt, change or deactivate owners. Bird's SCIM page names no plan. Read how SCIM and SAML differ.

How does Corma connect to Bird?

API keys cannot hold Bird's members scope, so member steps run as a person: Corma's browser-based agents can handle them in the Bird dashboard under Settings > Team, in an isolated browser session with credentials taken from your password vault. See also how Corma covers 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 every Bird leaver followed by a key rotation check? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!