BoondManager

BoondManager

Govern BoondManager (Boond) with Corma: manager accounts, Super utilisateur and intranet roles, deactivation without data loss, Google or Microsoft login.

The Corma and BoondManager integration keeps your Boond workspace, its manager accounts and its intranet access in line with the managers, consultants and subcontractors who use them. The vendor's terms describe BoondManager as an integrated, configurable management software available online and aimed at IT services companies and consulting and engineering firms, and its blog announced the new name Boond. Pricing is per manager per month, with a fee per consultant on most plans: the Core plan costs 59 € excl. VAT per manager and 4 € per consultant per month (seen on November 16, 2026).

Key takeaways

  • Boond workspaces come with four default roles: a manager role, Super utilisateur, with access to everything, and three intranet roles for employees, freelancers and subcontractors.
  • The number of Boond manager accounts is set in the subscription's specific terms and can be changed on request.
  • A deactivated Boond manager loses all access, intranet and manager, while their records stay accessible according to each user's rights.
  • Boond caps API usage per manager per month, from 500 calls on the Core plan to 50,000 on the Enterprise and Business plans.

What happens when a Boond manager leaves?

Records stay, access goes. Boond's help article on deactivating a manager explains that a former manager has no access left, and that their records remain accessible according to each user's rights, although their perimeter can no longer be used as a filter. A resource that has or had a manager profile cannot be deleted, to keep the data history consistent. Admins can make login through a trusted third party mandatory, with sign-in buttons for Google, Microsoft or Trustelem.

Integrations need the same care. Boond's API best practices warn that an integration running on a named employee's account does not stop when that employee changes role or leaves: it keeps running with less data and no visible error. OAuth2 access goes through an App that declares a precise API scope, and the Espace développeur right lets a manager create apps and access the API token. Boond says it is ISO 27001 certified and hosts data in France.

How Corma governs BoondManager

  • Manager accounts in the budget: the Boond subscription, with its manager accounts and consultant fees, sits in SaaS subscription management.
  • Leavers with an integration check: a leaver workflow in the IT Workflow Builder asks an administrator to move any integration running on the person's account to a dedicated account first, then to deactivate their manager account.
  • Roles under review: Super utilisateur and roles with the Espace développeur right go into automated access reviews.
  • Apps with an owner: OAuth2 apps and API tokens are non-human identities, so each one needs a named owner.

Frequently asked questions

Does BoondManager support SSO and SCIM?

Boond lets an administrator require authentication through a trusted third party, with Google, Microsoft or Trustelem, but its pages do not mention SAML or SCIM provisioning. Learn what single sign-on covers.

How does Corma connect to BoondManager?

Through the Boond REST API where it fits, whose accounts resource can search, create, update and delete accounts, or through Corma's browser-based agents in the Administration interface. See also how Corma covers HR tools such as Lucca.

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 every Boond leaver's integrations moved before their account is deactivated? Book a Corma demo.

Related Integrations

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