Ashby

The Corma and Ashby integration keeps Ashby seats and permissions in line with your hiring team, from recruiters to the managers who only leave feedback. Ashby describes itself as all-in-one recruiting software that covers the whole recruiting workflow: ATS, CRM and sourcing, scheduling and analytics. Recruiting data is candidate personal data, so who holds Elevated Access or admin rights matters for cost and for privacy.

Key takeaways

• On seat-based Ashby accounts, Elevated Access and Organization Admin users take a paid seat, while Limited Access and Agency users are free.
• A paid Ashby seat stays billed until the end of the subscription term, and the seat count can only go down at renewal.
• Deactivating an Ashby user removes them from interviewer pools but not from interviews already scheduled, which must be rescheduled by hand.
• Ashby supports SAML and OIDC SSO and SCIM directory sync through WorkOS, and users synced with SCIM arrive as Limited Access.

What should IT check before an Ashby user leaves?

Ashby offers two ways out. Deactivating a user removes access and brings them back as Limited Access if reactivated, while terminating also strips all their access roles, and profiles currently cannot be deleted. Interviews already on the calendar are not reassigned. In the Google Workspace integration, shared-calendar sync relies on individual users' Google access, so another active user must get the shared calendar before someone is deactivated.

Seats follow a yearly rhythm. Ashby's seat-based pricing charges for Elevated Access and Organization Admin users, and a paid seat stays billed through the subscription term. Moving people who only submit feedback to Limited Access, the permission set Ashby recommends for them, matters most before renewal. API keys are created only by Organization Admins, start with no permissions, and show who created them and when they were last used.

How Corma governs Ashby

• Paid seats matched to recruiters: Corma flags inactive Elevated Access and admin users, so the paid seat count is right before renewal, a core step of license management.
• Offboarding with an interview check: a leaver workflow in the IT Workflow Builder asks the recruiting team to reassign scheduled interviews and shared calendar access before the person is deactivated in Ashby.
• Candidate data under review: Elevated Access and Organization Admin roles go into automated access reviews, so access to candidate profiles is confirmed on a schedule.
• Hiring managers on request: hiring managers ask for Ashby in the self-service app store, and the approver confirms whether Limited or Elevated Access is needed.

Frequently asked questions

Does Ashby support SSO and SCIM?

Yes. Ashby supports SSO over SAML and OIDC and SCIM directory sync through WorkOS, naming Google Workspace, Microsoft Azure AD and Okta. SSO is included on Plus and Enterprise and is a paid add-on on Foundations, and SCIM is available on Legacy Plus, Plus and Enterprise. Turning on directory sync deactivates Ashby users who are not in the directory. Read what SCIM automates.

How does Corma connect to Ashby?

Through Ashby's API where it fits, which can list users including deactivated ones, or through Corma's browser-based agents for steps such as changing permissions. Corma's approach for people tools is described on our page for HR teams.

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 can still open candidate profiles in Ashby? Book a Corma demo.