Atlas.so

The Corma and Atlas.so integration keeps Atlas seats and roles in line with your support team. Atlas describes itself as an AI-first customer support platform that brings every customer conversation, the customer's full context and its Zeus AI into one workspace. A support tool reads customer conversations all day, so who holds an Atlas seat, and with which role, matters for cost and for privacy.

Key takeaways

• Atlas prices its Basic, Standard and Pro plans per seat, per month, with usage charges for SMS, WhatsApp and extra session recordings on top.
• Each Atlas user has one role, Admin, Agent or Viewer, and new teammates are added as Viewer by default.
• Removing an Atlas teammate means archiving them: access is revoked instantly and their history is kept.
• Atlas API keys are an Admins-only feature, and the API can post a ticket reply as any agent ID passed in the call.

Where does Atlas access need a second look?

Roles first. Atlas roles are Admin, Agent and Viewer, and Viewers can read conversations and export a ticket as PDF but cannot reply. The API's create-user call accepts five access types, ADMIN, MEMBER, LIGHT, CONTRACTOR and VIEWER, which is more than the three roles the help center describes, so it is worth checking how accounts created through integrations appear.

Departures and credentials come next. Removing a teammate archives them rather than deleting them, which keeps their history in place. API keys are created by Admins, and the documented call to send a message as an agent posts a reply as whichever agent ID the caller passes. Atlas does not document whether a key keeps working after the Admin who created it is archived, so every key deserves an owner and a regular check.

How Corma governs Atlas.so

• Seats in view: the Atlas subscription, its cost and its renewal sit in SaaS subscription management, and Corma flags inactive teammates before you renew.
• Leavers archived on time: a leaver workflow in the IT Workflow Builder archives the person in Atlas, or routes the task to an Atlas Admin, as soon as the HR system records the departure.
• Admin rights under review: Admin roles, which control API keys and team settings, go into automated access reviews.
• Requests with a role: new support hires ask for Atlas in the self-service app store, and the approver confirms Agent or Viewer before the invitation.

Frequently asked questions

Does Atlas.so support SSO or SCIM?

The Atlas pricing page lists SSO/SAML on the Pro and Enterprise plans, but the help center has no setup guide and its sign-in article describes email and password only. SCIM is not mentioned. Admins can make two-factor authentication mandatory for every teammate. Learn what single sign-on covers.

How does Corma connect to Atlas.so?

Through the Atlas API where it fits, or through Corma's browser-based agents, which work in the Atlas settings like an Admin would. Corma governs other support tools the same way, such as Zendesk.

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 answer your customers in Atlas? Book a Corma demo.