Accelo

Accelo

Connect Accelo to Corma to hand over work before deactivating leavers, review who sees billable rates and catch users created by a first Google sign-in.

The Corma integration for Accelo connects your PSA to the HR record, so a departure triggers a proper handover of projects, tickets and client accounts before the user is deactivated. It is aimed at agencies, consultancies and IT service firms where Accelo holds billable rates, time and client data.

Key takeaways

  • Accelo has three license types (Administrator, Professional and Contractor), and inactive users are not charged in the next billing cycle.
  • Deactivating an Accelo user opens a bulk reassignment wizard that moves work module by module to a single colleague.
  • Accelo permissions add up across user groups, so a user in several groups holds every permission any of those groups grants.

How is access structured in Accelo?

Accelo stacks permissions on five levels: user license, financial visibility, user groups, individual users and individual objects. Financial visibility decides whether someone sees hours only, or hours plus billable rates and budgets. Contractors see only the work assigned to them and are billed on hours worked.

Sign-in runs through Google Workspace or Microsoft 365 single sign-on, and SAML is offered as a beta. With the Google Workspace integration, Accelo can also create a user automatically the first time a team member logs in.

Why is offboarding in Accelo more than a deactivation?

In a PSA, a user also owns work. Before deactivation, their sales, projects, tickets and retainers need a new owner, and the wizard sends each module to one person only. Once the account is inactive, its timesheets and schedules are no longer accessible, so pending time is best approved first.

Two quieter issues build up over time. Group permissions accumulate as people move between teams, widening who sees billable rates. And automatic creation through Google sign-in can add users outside your approval process.

What Corma automates for Accelo

  • Handover first: the leaver workflow names who takes over each module, then deactivates the account once the work has moved.
  • Movers covered: as part of the joiner-mover-leaver cycle, group memberships are reviewed when someone changes team, so old permissions do not stay.
  • Financial visibility reviews: users who can see rates and budgets are reviewed on a schedule, a control that supports separation of duties.
  • Roster check: Corma compares Accelo users with your HR list and flags accounts created at first sign-in without an approved request.
  • License tracking: Administrator, Professional and Contractor licenses are tracked against real use as part of your license management.

Accelo integration FAQ

Does Accelo support SCIM?

Accelo does not document SCIM. It offers Google Workspace and Microsoft 365 sign-in, SAML in beta, and an OAuth 2.0 API with staff endpoints. Corma handles user provisioning on top of these, including the steps done in the Accelo interface.

Does deactivating a user in Accelo delete their history?

No. Accelo keeps the user's history, activities and files, and reactivating the account restores access. Inactive users stop counting as active licenses from the next billing cycle.

Where is Accelo data hosted?

Accelo runs on AWS with an EU region in Ireland, alongside US and Australian regions, and offers a GDPR data processing addendum. Corma runs on AWS inside the European Union and is ISO/IEC 27001:2022 certified.

Running client work in Accelo? Book a demo to see a leaver handover done end to end.

Related Integrations

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