Ahrefs

Ahrefs

Govern Ahrefs with Corma: per-user seats and add-ons, Owner and Admin roles, API keys tied to their creator, and clean offboarding before renewal.

The Corma and Ahrefs integration keeps Ahrefs users and roles in line with your marketing team, and the per-user add-ons in line with your budget. Ahrefs describes itself as a SaaS marketing platform that helps marketers make their brands discoverable online, with tools such as Keywords Explorer and Rank Tracker. On Standard and Advanced, where each extra user is a flat monthly add-on, a seat left to a former colleague is money spent on nothing.

Key takeaways

  • Ahrefs Lite, Standard and Advanced plans each include one user, and extra users are monthly add-ons capped by plan.
  • All members of an Ahrefs workspace share the usage limits of that workspace.
  • A removed Ahrefs member loses access immediately, but a freed paid seat is only released at the end of the billing period.
  • An Ahrefs API key is invalidated when the user who created it is removed from the workspace.

Where do Ahrefs costs and access drift?

Ahrefs prices access per user. On the Ahrefs pricing page, the Lite, Standard and Advanced plans each include one user and cap how many more you can add, each billed monthly, while Enterprise starts from three users. Removing a member cuts access at once, but if that frees a paid extra seat, the User seats add-on stays in a pending downgrade until the end of the billing period.

Roles are simple: Owner, Admin and Member, plus Guest on Enterprise plans. The Owner is the person who registered the account and cannot be changed from within Ahrefs. Only Owners and Admins can remove members or create API keys, and a key is invalidated if the user who created it is removed. A marketing ops lead who leaves can take reporting integrations down with them.

How Corma governs Ahrefs

  • Seats matched to the team: Corma shows who holds an Ahrefs seat and flags people who left or stopped using it, the first step of software license optimization.
  • Offboarding without broken reports: a leaver workflow in the IT workflow builder can ask an Ahrefs admin to move integrations to a key owned by someone who stays, then remove the member.
  • Requests before add-ons: new marketers ask for Ahrefs in the self-service app store, and a manager approves the extra seat before it is added.
  • Admin rights under review: Owner and Admin roles, the only ones that can remove members or create API keys, go into automated access reviews, since each key they create is a non-human identity that can stay valid for up to 10 years.

Frequently asked questions

Does Ahrefs support SSO and SCIM?

SAML SSO is available on Ahrefs Enterprise plans and can be made the only sign-in method, although the workspace owner and admins can always sign in with email and password. Ahrefs also documents SCIM: users assigned to the Ahrefs app in your identity provider are added to the workspace, and unassigned users are removed. Enabling it goes through Ahrefs support. Read what SCIM automates.

How does Corma connect to Ahrefs?

Through an API integration where Ahrefs allows it, or through Corma's browser-based agents, which work in the Ahrefs account settings in an isolated browser session. Teams on Lite, Standard or Advanced can still automate member changes this way, with an Owner or Admin login taken from your password vault.

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 see who still holds an Ahrefs seat? Book a Corma demo.

Related Integrations

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