Groups and subsidiaries
A parent company and its subsidiaries are linked. The parent sees counts from each company that chooses to share them, never a case.
Enterprise
One programme across every company in the group
Each company keeps its own portal, address and key. The parent sees counts across the group, people sign in through your identity provider, joiners and leavers stay in sync, and your other systems hear about cases without seeing what is in them.
What it does today
Single sign-on
Through OpenID Connect: Microsoft Entra ID, Google, or another provider such as Okta. Employees sign in with the account they already have.
Directory sync
SCIM 2.0 from your identity provider keeps people up to date: joiners can sign in, leavers can't.
The reporting API
Read-only case facts, a page at a time, by key, for Power BI or a data warehouse. Never report text, names or files, and no location on anonymous reports.
Signed webhooks
A case opened or closed, a check-in that raises a concern, a declaration submitted. Each carries references only, is signed with HMAC-SHA256, and is retried for about 12 hours.
Roles that fit the organisation
Roles with their own permissions, each limited to the categories and locations it should see. People in a case lose access to it.
For your developers
The reporting API and directory sync are described in OpenAPI 3.1, at the addresses integrators use, with no company data in the file.
Said plainly
- Single sign-on is OpenID Connect. SAML isn't offered.
- Directory sync covers people. Groups in your directory aren't synced.
- Group counts include only the companies that switch sharing on, and only counts.
- We set single sign-on and directory sync up with your IT team when you go live.
Coming soon
- Coming soonAn API reference pageThe same description, drawn as pages people can read, next to the file above.
See it with your own questions
A walkthrough of the screens on this page, set up around your company.