Acuity Scheduling

The Corma integration for Acuity Scheduling treats staff logins and calendars as two separate things, because Acuity does: removing a person's login and retiring their calendar are different steps with different consequences. It helps IT teams in clinics, agencies and service businesses where client bookings and intake forms live in Acuity.

Key takeaways

• Acuity Scheduling plans are capped by calendars (1 on Starter, up to 6 on Standard, up to 36 on Premium) rather than charged per user.
• Acuity staff logins have one of three access levels (View Only, View & Edit or Admin) and can be limited to specific calendars and to exporting client information or not.
• Deleting an Acuity calendar keeps its appointments but removes them from every calendar and stops their reminder emails.

How do logins and calendars work in Acuity Scheduling?

Acuity separates the person from the calendar. A calendar holds availability and appointments, while a login gives someone access to one or more calendars. The account owner adds staff with View Only, View & Edit or Admin access, chooses which calendars each person sees and decides whether they can export appointments and client details.

Single sign-on comes with the Enterprise plan. Other plans sign in through Squarespace accounts with two-factor authentication. No SCIM support is documented, and the API, available from the Premium plan, covers appointments, availability and clients but not users.

What goes wrong when a staff member leaves?

Two things can go wrong at once. If the login stays, a former employee can still see client names and intake form answers and, depending on their permissions, export them. If the calendar is deleted in a hurry, future appointments drop off every calendar and clients stop receiving reminders. Acuity advises rescheduling, cancelling or exporting those appointments first.

Calendars also drive cost. Staying within 6 calendars keeps you on Standard and within 36 on Premium, so retired calendars should not linger.

What Corma automates for Acuity Scheduling

• Login removal on the last day: the departure in your HR tool triggers removal of the Acuity login, performed by Corma's AI agents because the API cannot manage users.
• Calendar handover: the leaver workflow asks the manager to move future appointments before the calendar is retired.
• Export rights under review: logins allowed to export client information are part of each access review.
• Plan fit: retiring unused calendars as part of offboarding keeps your calendar count, and your tier, where it should be.
• One inventory: Acuity sits next to the rest of your apps, so IT teams see every login in one place.

Acuity Scheduling integration FAQ

Does Acuity Scheduling support SSO or SCIM?

Single sign-on is part of Acuity's Enterprise plan. Other plans rely on Squarespace login with two-factor authentication, and no SCIM support is documented. Offboarding therefore happens in the Acuity interface, which Corma automates.

What happens to appointments when an Acuity calendar is deleted?

They are kept, but they no longer appear on any calendar, no reminders are sent, and reports mark them as belonging to a deleted calendar. Only Acuity support can restore a deleted calendar.

Where is Acuity data hosted?

Acuity states that its Enterprise plan is hosted on AWS in the United States. For EU companies, that is a data sovereignty point to document, especially when intake forms collect sensitive information. Corma runs on AWS inside the European Union.

Running client bookings in Acuity? Book a demo to see a staff departure handled end to end.