Skip to content
Review the supplied policies
Public Preview

Default policies: permissions, membership, and audit

Describes permissions, membership rules, and audit records for Duale AI's five supplied policies, from Administrator to Tenant-member identity read.

This page covers the supplied policies, group membership changes, Library operations, and audit records for supplied policy updates.

  • Supplied policy permissions and group assignments.
  • Changing membership in supplied groups.
  • Library operations allowed by each supplied policy.
  • Audit records for supplied policy changes.

Summaries were generated by AI.

Duale AI supplies the Administrator, Editor, and Viewer policies for people, and the Agent default and Tenant-member identity read policies. Duale AI sets and updates their permissions and the groups that hold them. The table below summarizes each one. For its exact permissions, open Policies and read the supplied policy’s Permissions list.

Review the supplied policies

Supplied policy, as named in PoliciesGroup display nameWhat it allows
Administrator: tenant-admintenant-adminsManages the whole Tenant, including policy and supplied-group management, Agent Identity token issuance, Library deletion and Grants, and Audit export.
Editor: tenant-editortenant-editorsReads members, groups, policies, Agent Identities, billing, analytics, and every Task; creates and updates configuration; reads and changes Libraries across the Tenant; creates Agent Identities and revokes their tokens. It cannot issue a token, edit or delete an Agent Identity, assign MCP Connections, delete configuration, author a policy, or read Audit.
Viewer: tenant-viewertenant-viewersRead-only access across the Tenant, including Audit records and their proofs. It cannot export Audit records.
Agent default: agent-defaultall-agentsCreates Tasks and runs a Tool Host only as itself; reads, continues, and stops its own Tasks; and uses Libraries under its own agent/<agent_id>/ path. Every Agent Identity inherits it.
Tenant-member identity read: tenant-member-identity-readtenant-membersReads members, groups, and Agent Identities. Every person receives it with Tenant membership.
  • Supplied policy, as named in Policies
    Administrator: tenant-admin
    Group display name
    tenant-admins
    What it allows
    Manages the whole Tenant, including policy and supplied-group management, Agent Identity token issuance, Library deletion and Grants, and Audit export.
  • Supplied policy, as named in Policies
    Editor: tenant-editor
    Group display name
    tenant-editors
    What it allows
    Reads members, groups, policies, Agent Identities, billing, analytics, and every Task; creates and updates configuration; reads and changes Libraries across the Tenant; creates Agent Identities and revokes their tokens. It cannot issue a token, edit or delete an Agent Identity, assign MCP Connections, delete configuration, author a policy, or read Audit.
  • Supplied policy, as named in Policies
    Viewer: tenant-viewer
    Group display name
    tenant-viewers
    What it allows
    Read-only access across the Tenant, including Audit records and their proofs. It cannot export Audit records.
  • Supplied policy, as named in Policies
    Agent default: agent-default
    Group display name
    all-agents
    What it allows
    Creates Tasks and runs a Tool Host only as itself; reads, continues, and stops its own Tasks; and uses Libraries under its own agent/<agent_id>/ path. Every Agent Identity inherits it.
  • Supplied policy, as named in Policies
    Tenant-member identity read: tenant-member-identity-read
    Group display name
    tenant-members
    What it allows
    Reads members, groups, and Agent Identities. Every person receives it with Tenant membership.

These groups also appear in the Groups list, marked Supplied. Policies explains how their permissions add up with those of your own groups.

Change who is in a supplied group

Before you add a person to a supplied group, review their access as Review access describes. Access from supplied groups adds up: to move a person from Editor to Viewer, add them to tenant-viewers and remove them from tenant-editors. Each supplied group gives its access across the whole Tenant. To keep a person away from some documents entirely, use a separate Tenant.

You need profile:manage_tier on the supplied group; profile:manage_group covers custom groups only. To add a member, you must also hold every permission that the group gives. Each change also needs the required sign-in level.

In the Dashboard, open Groups, choose the supplied group, then use Members > Add member or Remove member. Duale AI refuses to remove, suspend, or demote the last active member of tenant-admins, so the Tenant always keeps an Administrator.

Duale AI adds every Agent Identity to all-agents and every member to tenant-members automatically. For more access, author a policy and bind it to a custom group.

Library operations in the supplied policies

Viewer reads every Library in the Tenant. Editor also creates, changes, and adds documents to Libraries anywhere in the Tenant. Of the supplied policies, only Administrator deletes documents and Libraries and manages their Grants.

By default, an Agent Identity can start a document upload, and it creates, reads, and writes Libraries only under its own agent/<agent_id>/ path. That path includes the Libraries that the SDK creates for its Task attachments. To reach another Agent Identity’s path, delete a document or a Library, or manage a Library’s Grants, an Agent Identity needs another policy or Grant. Library access and isolation explains creation and Grants.

See what Duale AI changed in a supplied policy

When Duale AI changes a supplied policy or the supplied group that holds it, it records the change in the audit history of each affected Tenant, with system as the actor.

In Audit Logs, select Supplied Policy as the resource type and Supplied policy · update as the action, then open the event. Its changes list the permissions added and removed, the groups bound to or unbound from the policy, and the resulting change in each group’s access.

The record shows changes per group, not per member. To find who gained or lost access, review each member of an affected group as Review access describes. Evidence and audit explains how to search, export, and verify audit records, and what they do not record.