Bitly

Bitly

Govern Bitly with Corma: Account admin, Group admin and User roles, Enterprise groups and seats, SAML SSO and SCIM, user API tokens that never expire.

The Corma and Bitly integration keeps your Bitly account, its groups and its users in line with the marketing teams who create your links and QR Codes. Bitly describes itself as a leading marketing platform for link and QR Code management, and it acquired Egoditor, the company behind QR Code Generator, in December 2021. Enterprise plans come with a user seat allocation, so who holds a seat matters for the contract as well as for your brand's links.

Key takeaways

  • Bitly has three roles: Users, who create links and view metrics, Group admins, who manage their groups' users and custom domains, and Account admins.
  • Bitly groups require an Enterprise subscription, and links and QR Codes stay in the group they were created in.
  • Bitly API access tokens are generated per user and never expire, and tokens created before Require SSO is turned on keep working afterwards.
  • SSO is included with every Bitly Enterprise subscription, but SCIM provisioning is not supported with Microsoft Entra ID.

What does a Bitly admin need to watch?

Tokens are personal and permanent. Bitly's help center explains that an API access token never expires and must be revoked and replaced manually if it leaks. Tokens are generated at user level, not for the organization, and Bitly does not document whether removing a user revokes their token. Once Require SSO is on, tokens created before it keep working, and no user, not even a contractor, can be exempted.

Admins can invite up to 50 users at a time by email address or Bitly username, and only an Account admin can remove a user, from Settings > Users. Bitly does not document what happens to a removed user's links. Bitly's user export shows each user's last active date and whether they have created an API token, and the activity log records users being added, removed and invited.

How Corma governs Bitly

  • Admins under review: Account admins and Group admins go into automated access reviews.
  • Leavers with a token check: a leaver workflow in the IT Workflow Builder asks an Account admin to check whether the person created an API token and which integration uses it, then to remove them from the account.
  • Integrations with an owner: integrations that run on a user's API token are non-human identities, so each one needs a named owner.
  • Seats in the contract: the Enterprise contract and its renewal date sit in SaaS subscription management, and users with an old last active date are candidates for license reclaim.

Frequently asked questions

Does Bitly support SSO and SCIM?

Yes. SSO is included with every Enterprise subscription, Bitly lists SAML 2.0 and SCIM 1.1 and 2.0 as supported standards without naming a plan for SCIM, and its supported identity providers are PingFederate, OneLogin, Google G Suite, Okta and Microsoft Entra ID. SCIM provisioning is not supported with Entra ID, so Entra ID customers manage provisioning manually in Bitly. Read how SCIM and SAML differ.

How does Corma connect to Bitly?

Bitly's v4 API returns information about the authenticated user but documents no endpoint to list or remove organization members, so Corma's browser-based agents can handle user steps under Settings > Users, in an isolated browser session with credentials taken from your password vault. See also how Corma covers Hootsuite.

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 Bitly leavers checked for API tokens before they go? Book a Corma demo.

Related Integrations

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