How is access scoped?

Through four layers that compose: Workspace, Space, Team and Campaign roles. Teams are granted specific Brands, and sub-teams inherit the grant unless it is overridden.

What does the audit log hold?

Per-entity change history with before and after values, plus a searchable Workspace-wide log. Agent actions sit in the same log, each carrying the reasoning behind it.

What stops an AI Agent doing something costly?

Spending caps per run, per day and per month; kill switches for one Agent or all of them; tool rules that default to human confirmation on every call; and an Autopilot level that defaults to Suggest Only.

Can Collabre staff see our content?

Only with time-boxed, owner-granted, read-only support access, and every action under it is recorded. Impersonation shows a persistent banner and is audit-logged.

Is there an enterprise price?

There is no enterprise plan in the product registry, so this site prints no enterprise price. Talk to us and we will work from what you need.

Collabre for enterprise

Q: Do you support single sign-on?

Yes. SAML single sign-on is configured per Workspace against your identity provider's endpoint and certificate, and a Workspace can require every member to sign in through it.

Screenshot pendingThe Governance dashboard with the Spending Caps tab selected and caps configured at all three levels: the three cap levels with their values, and the tab row showing Spending Caps, Kill-Switch, Tool Allow/Deny Rules, Destructive Actions and Audit Log.

Accounts and access

Access is layered and the layers compose: Workspace roles, Space roles, Team roles and Campaign roles. Teams are granted access to specific Brands, inherited by sub-teams unless overridden. People sign in with a password, a magic link, Google, or SAML single sign-on configured per Workspace against your identity provider's endpoint and certificate. The Workspace can require two-factor authentication, which uses a time-based code with backup codes, and it can require every member to sign in through the identity provider. A login activity log records method, location and failures.

Connect your identity provider and require single sign-on for every member.
Require two-factor authentication for everyone in the Workspace.
Scope a Team to the Brands it works on, and nothing else.
Read the login activity log when an account looks wrong.

Screenshot pendingSecurity settings with the Two-Factor Auth tab selected and enforcement on: the tab row, the enforcement control, and the backup code action.

The audit log

Auditing works at two levels. Each entity carries its own change history with the values before and after, and the Workspace carries a searchable log for compliance. Agent actions land in the same place, each with the reasoning behind it, so a review of what the AI workforce did reads as one record rather than a set of exports.

Search the Workspace log by actor, entity or date.
Open an entity's history and read the before and after values.
Export a compliance report from the governance dashboard.

Screenshot pendingThe audit log with entries from both people and Agents: the search and filter row, the actor column showing a person and an Agent, and one expanded entry with its before and after values.

AI governance

Spending caps apply per Agent run, per Agent per day and per Workspace per month. Kill switches halt one Agent or every Agent at once. Tool approval rules allow, deny or require confirmation for any tool, scoped to the Workspace, an Agent, a Department or a Campaign, defaulting to human confirmation on every call. Destructive actions are classified as automatic, human-in-the-loop or denied, and PII redaction is on by default.

Set the caps, then watch spend and the forecast against them.
Deny a tool outright for the Workspace, or require confirmation on each call.
Set the Autopilot level per Campaign; it defaults to Suggest Only.

Screenshot pendingThe Governance dashboard with the Tool Allow/Deny Rules tab selected and rules at Workspace and Campaign scope, including one deny: the rule list with its scope, tool and decision columns.

White-label

A Workspace can run under its own name: a custom domain, a Brand name, a logo, primary and accent colors, custom CSS, a branded login page, an email sender name, and report header and footer markup. What reaches an internal audience or a client carries your identity rather than Collabre's.

Point a custom domain at the Workspace and set the logo and colors.
Brand the login page your people see every morning.
Write the report header once, and every scheduled report uses it.

Screenshot pendingWhite Label with a saved configuration: the Brand Name and Custom Domain fields filled, the primary and accent color pickers, and the report header field with markup in it.

API keys and webhooks

API keys carry scopes and rate limits, so a system reads only what it should and cannot flood the API. Webhooks push Collabre events to external systems, and feature flags carry per-Workspace overrides for staged rollouts. Analytics and report data export to CSV and PDF for the systems that prefer a file.

Issue a scoped key per integration, and revoke one without touching the rest.
Subscribe a system to the events it needs, and read the delivery status.

Screenshot pendingAPI Keys with two active keys carrying different scopes: the key list with scopes, the rate limit on each, and the revoke action.

Support access

Collabre staff cannot wander into a Workspace. Support access is granted by an owner, time-boxed, and read-only, and every action taken under it is recorded. When a Super Admin enters a Workspace as a user for support, a persistent banner shows it and the session is audit-logged.

Grant support access for a fixed window when you raise an issue.
Read the audit log afterwards to see exactly what was viewed.

Content operations a compliance team can read