Enterprise
Roll it out once. Govern it properly.
Identity, provisioning, device management and DLP at the platform layer — so the rollout is a configuration exercise, not a negotiation.
What IT asks first
Who can see what
Capability-based access with row-level security on every query, including the AI layer's.
Where the data lives
EU or UK residency, chosen per workspace, with every subprocessor listed publicly.
How people get access
SAML for sign-in, SCIM for lifecycle. Deprovisioning is immediate and audited.
What the AI can reach
Only what the asker could already open. Direct messages are never used as context.
Identity and device
Messages pass a policy gate before they are stored. Anything matching a secret pattern is redacted and replaced with a reference to the secrets manager, so the credential itself never lands in the channel.
Migration at scale
Import an export from your current chat tool, connect the systems of record, let the index build, then provision everyone through SCIM. Teams of a few hundred typically run both in parallel for two weeks and then stop.
Switching
Move in an afternoon.
- 1
Import
Channels, threads and files from whatever you use now — structure intact.
- 2
Connect
Point Huub at GitHub, Drive, your CRM. Ten minutes each.
- 3
Index
Enterprise search and the agent build their memory in the background.
- 4
Invite
SCIM provisions everyone. Nobody creates a password.
Procurement
- Security review pack, including architecture and subprocessors.
- DPA available on request, with EU and UK residency options.
- Annual invoicing, purchase orders and an SLA on Enterprise.
“IT signed off in one meeting. SAML and SCIM were already there, so there was nothing to negotiate up a tier.”
Stop paying to forget.
Get a walkthrough with the team that runs its own company on Huub.