A ZeroTwo Business workspace controls access in layers: member roles and the admin console, workspace policies and app settings, sharing on individual items, and permission presets for the agent's own actions. Having access in one place never grants it in another.
Understand the control boundaries
| Boundary | Governs | Does not govern |
|---|---|---|
| Workspace roles and the admin console | Members, groups, invitations, seats, billing, identity | Access to a specific space, page or Site |
| Workspace policies (General) | Which features members can use | What an individual item is shared with |
| Apps in the admin console | Which connectors and tools members can use, and their approval policy | Rights inside the connected service |
| Sharing on spaces, pages, projects, Sites | Who can view or edit that one item | Workspace role |
| Agent permission presets | What a local run may do without asking | Seats, models, workspace policies |
A connector may be enabled for the workspace while the source system still limits what the signed-in account can read or change.
Assign workspace access
Every member holds one of three built-in roles: Owner, Admin or Member. Owners and admins can open the admin console, invite people and manage the workspace; only an owner can make someone else an owner, and only owners can manage payment methods, invoices, credits and cancellation. Each member also has a seat type, Standard or Premium, which sets their monthly usage limit under Billing.
Change a member's role or seat type from their row under Members > Users. Use Groups to collect members and assign roles to them together; groups provisioned through SCIM are managed by your identity provider.
Use permissions and custom roles
Permissions & roles has a Workspace tab listing 29 permissions in sections, such as enabling skills, web search and Code Cloud, with a search box. The same switches appear under Workspace policies on the General page, and they apply to everyone in the workspace. Switches take effect for features such as web search, memory, Code, Record, Sites and Bots, and a switch marked Coming soon has no feature behind it yet.
Admins can choose Create role to define a custom role with a name, an optional description and Default, Allow or Deny for each permission, then assign it to members or groups.
Custom roles and their assignments are saved, but ZeroTwo does not apply them to members' access yet. Use the workspace-wide policies to turn features on or off.
Share specific content
| Item | Roles |
|---|---|
| A space | Owner, Admin, Can edit, Can view, invited by email |
| A page, slide deck or library file | Can edit or Can view |
| A project (Share project) | Can view (chat and view content), Can edit (edit files, chat, manage content) or Admin (full project access, invite members) |
| A Site (Who has access) | Only you, Restricted access, or Anyone with the link |
| A chat or message | A public link for signed-in users; see Share chats and messages |
Spaces and pages are shared by email address. Sites can also take access groups scoped to the organization or workspace, with Viewer, Editor or No access.
Apply local runtime policy
On desktop, the composer's permission presets are Ask for approval, Approve for me (the default) and Full access. They affect only the agent's own actions and are set per person, not by an administrator, and a workspace's approval policy for connectors still applies under Full access; the web app has no preset picker because cloud runs execute in an isolated sandbox. Scheduled tasks always run with Full access. For connectors, the admin console's Manage app dialog sets the workspace's approval policy for each app's tools.