Skip to content

Enterprise Roles

An Enterprise account has two layers, each with its own roles:

  • The enterprise is your company: its email domains, sign-in rules, people and contract. Enterprise roles decide who manages those.
  • Organizations sit inside the enterprise and own apps. Organization roles decide who can see and ship each organization’s apps.

The two are separate. An enterprise role gives no access to any app, and an organization role gives no say over the enterprise. One person can hold both.

Everyone who signs in with a managed account at one of your domains (through Google Workspace, Microsoft Entra ID, or your SAML connection) is a Member of your enterprise automatically. When Shorebird sets up your enterprise, you name its first Owners, Admins and Billing managers and who should own your organization; everyone else joins as a Member. From then on, Owners change roles from the People tab of the Enterprise page in the Shorebird console. Owners and Admins can also add a person before they first sign in. Owners, Admins and Billing managers find Enterprise in the sidebar and in the account menu.

MemberBilling managerAdminOwner
See every organization, app, person and API key✅✅
See activity across organizations✅✅
Read the enterprise audit log✅✅
Download the access report✅✅
Add a person before they sign in (an Admin adds only Members)✅✅
Add people to any organization and change their role✅✅
Make someone an organization’s owner✅✅
Deactivate a person other than an Owner (an Admin deactivates only Members)✅✅
Remove guests and set the guest policy✅✅
Set default organizations✅✅
Turn required patch signing on or off✅✅
Add and remove enterprise-wide freeze windows✅✅
Override a freeze window in apps they can promote patches in✅✅
See service accounts and revoke API keys✅✅
Create Auditor service accounts and their keys✅✅
Add and manage the enterprise’s webhooks✅✅
Change enterprise roles✅
Require a sign-in method for a domain✅
Create the SCIM account✅
See billing, usage and invoices✅✅
See and download contracts✅✅

Only an Owner can create or revoke the SCIM account’s keys, or delete it. An organization’s new owner must already be a member of it, and if its current owner holds an enterprise Owner, Admin or Billing manager role, only an enterprise Owner can make the change; see On the Enterprise plan.

An enterprise always has at least one Owner; the last one can’t be demoted, and an Owner can’t be deactivated until they’re given another role.

Deactivating a person takes them out of every organization in the enterprise that they don’t own and every app in the enterprise they were granted, and revokes their sessions, API keys and pending invitations to them.

Guests are people outside your domains who belong to one of your organizations. The guest policy decides whether organizations can add them.

Default organizations are ones that your enterprise’s Members join on their own, as a Viewer or Developer, whenever they sign in with a managed account through Google, Microsoft or your SAML connection. Owners, Admins and Billing managers don’t join them; add them to an organization yourself if they need app access. Someone removed from a default organization rejoins it the next time they sign in. To keep someone out, deactivate their account, which also stops them signing in.

To choose default organizations, open the Organizations tab of the Enterprise page. In the Default organizations card, click Add default organization, pick the organization, and choose the role Members get under Joins as. Remove on an organization’s row takes it off the list after you confirm. You can also select an organization on that tab and turn on Add enterprise members at sign-in in its Default organization section. It starts at Viewer; change the role in the menu that appears beside it. Adding or removing a default organization doesn’t change anyone already in it.

Activity across organizations shows each app’s name, organization, release versions, channels and install counts. To open an app, create a release, or publish a patch, a person needs an organization role in the organization that owns it, even if they are an enterprise Owner.

This keeps people who manage the account or pay for it, such as IT or accounts payable, from shipping to your users by default. An engineer who is also an enterprise Admin holds both roles and gets both sets of abilities.

Enterprise Admins and Owners can still reach any app, because they can add anyone in your enterprise to any of its organizations, themselves included, with any role the organization’s plan offers except Owner. They do it from the Organizations tab of the Enterprise page: select the organization and click Add member. The person is added at once, with no invitation, and the organization’s audit log records it as organization_member.add. Give these two roles only to people you’d trust with your apps.

The access report lists everyone who can reach your enterprise’s apps, and how. On the People tab of the Enterprise page, click Download access report to get it as a CSV file. Enterprise Admins and Owners can download it.

It has a row for each way a member, guest, or service account reaches your apps: each organization they belong to, with its apps and their role there, and each app they collaborate on. Someone with no access gets one row with those columns empty. Each row also has their enterprise role, how they sign in, and when they last signed in and were last active. Use it for periodic access reviews.

Add someone at your domains before they first sign in, for example to put them in organizations ahead of their start date. On the People tab of the Enterprise page, click Add person and enter their email and, if you like, a name; without one, their name is the part of the email before the @. Shorebird emails them that they were added. Their first sign-in with that email, by a sign-in method your domain allows, uses this account.

An enterprise Owner chooses the person’s Enterprise role; an Admin adds Members only. To also add them to organizations, select those under Organizations and choose an Organization role, Viewer or Developer. Each of those organizations also emails them. If an organization can’t add them, they’re still added to your enterprise and the console names that organization, so you can add them from the Organizations tab.

The console refuses an email that isn’t at one of your domains, or that already has a Shorebird account. If that account was deactivated, reactivate it instead.

Deactivate offboards a person in one step. On the People tab of the Enterprise page, open the person and click Deactivate. Enterprise Admins and Owners can do this, and only an Owner can deactivate an Admin or Billing manager.

To deactivate several people together, select the checkbox on each of their rows, then click the button above the list that counts them, such as Deactivate 3 people. A row’s checkbox is disabled for yourself, for an enterprise Owner, and, if you’re an Admin, for an Admin or Billing manager. You select people one page of the list at a time; the checkbox at the top of the list, labeled Select all on this page when the list is narrow, selects every row on the page that you can deactivate.

A deactivated person:

  • Loses every organization in your enterprise that they don’t own, and every app in your enterprise they were granted.
  • Is signed out everywhere, and their API keys and pending invitations to them are revoked.
  • Can’t sign in to Shorebird.

The account and its history are kept. To see who was deactivated, click Deactivated beside Members in the Enterprise members section. Reactivate lets someone sign in again, with the enterprise role they held, as long as they’re still on one of your domains. Only an Owner can reactivate an Admin or Billing manager. Nothing deactivating took comes back: organizations, app access, invitations, sessions and API keys stay gone. A reactivated Member rejoins your default organizations the next time they sign in.

To deactivate an enterprise Owner, give them another role first. Organizations a deactivated person owns stay theirs, and their apps keep working; give each one a new owner whenever you’re ready. With SCIM, your identity provider deactivates people when they leave.

The guest policy sets who outside your domains the organizations in your enterprise may invite. On the People tab of the Enterprise page, click Guest policy in the Guests section and choose one:

  • No guests. Only people at your domains can be invited.
  • Guests from these domains. People at your domains and at the domains you list, such as an agency’s.
  • Anyone. Organizations may invite anyone.

Guests already in your organizations keep their access under a stricter policy. The console marks them Outside guest policy.

To remove a guest, open the ⋮ menu next to them in the Guests section and choose Remove guest. They lose every organization and app in your enterprise, and pending invitations to them are revoked; their Shorebird account stays. Remove all guests removes every guest, not only those outside the policy. A guest who owns an organization can’t be removed, and Remove all guests skips them; give the organization a new owner first, then remove them.

The API keys card on the Security tab of the Enterprise page lists every key that can act in your enterprise’s organizations, including ones you aren’t a member of: Service account keys, which service accounts use in CI and scripts, and Personal keys, which members created for themselves. Expired keys aren’t listed.

To revoke one, open the ⋮ menu on its row, choose Revoke key, then click Revoke. The key stops working at its next request, so anything using it, such as CI, fails until it gets a new key. Revoking can’t be undone. Enterprise Admins and Owners can revoke keys, except the SCIM account’s, which only an Owner can revoke.

Each organization has its own members, each with one of Viewer, Developer, App Manager, Admin or Owner. These roles apply to every app in that organization. See Member roles for what each one can do.

Organization Admins and Owners manage their organization’s members. They don’t need an enterprise role to do it.

Most companies divide the work like this:

WhoEnterprise roleOrganization role
The engineering champion for ShorebirdOwner or AdminOwner of the app’s organization
An engineering manager, CTO or contract ownerOwnerNone, or Viewer
Accounts payable or procurementBilling managerNone
The rest of the mobile teamMemberDeveloper or App Manager
  • Owners control who holds each role, whether your domains must sign in through SSO, and your contracts. The engineering champion can be an Owner when your company doesn’t mind engineers seeing the contract; otherwise make them an Admin and give Owner to a manager. Keep at least two Owners, so the account isn’t stranded when one leaves.
  • Admins handle people day to day: they deactivate Members who leave, manage guests, revoke stray API keys and watch the audit log.
  • Billing managers see billing, invoices and contracts, without access to your people or apps.
  • The organization’s Owner invites the mobile team, sets each person’s organization role, and manages releases and patches. Organization roles are what grant access to apps.

If one person does more than one of these jobs, give them each role it needs.