Yes. Brilo AI Permission Levels let administrators assign different control levels to different teams so each group only sees and can change what they need. Permission Levels support role assignment, team-level access controls, and granular permissions to restrict features such as call routing, agent training, and account settings. Administrators configure these controls in the Brilo AI admin console and map roles to teams or permission groups; audit logs record changes for review. This enables least-privilege operation while preserving centralized governance.

Can admins set team-based permissions? — Yes. Brilo AI admins can assign role-based access to teams so each team has a tailored permission set.

Can different teams have different access? — Yes. Use team-level access controls (permission groups) to enable or limit features per team in Brilo AI.

How are permissions assigned? — Permissions are assigned by creating roles and mapping those roles to teams or individual users via Brilo AI’s admin settings.

Enterprises ask this because organizations often have multiple lines of business (for example, clinical support, fraud operations, and claims teams) that require different capabilities inside Brilo AI. Buyers want to avoid overprivileging users while keeping operations efficient. They also need clear auditability for compliance and to separate duties between teams that manage voice agent training, call routing, and reporting.

Brilo AI Permission Levels are implemented through role assignment and team mapping inside the Brilo AI admin console. Administrators create roles that bundle capabilities (for example: view-only reporting, manage agents, or configure routing) and then assign those roles to teams or individual users. Brilo AI enforces those permissions at runtime across the console and API endpoints so users only see features and data their roles allow.

In Brilo AI, Permission level is a named set of enabled and disabled capabilities applied to users or teams.

In Brilo AI, Role is a reusable profile that includes a set of permissions such as agent editing, routing configuration, or audit viewing.

Related concepts in Brilo AI include role-based access control (RBAC), granular permissions, scopes, and audit logs for change tracking.

Brilo AI Permission Levels are designed to reduce risk but have clear boundaries. Brilo AI does not automatically infer least privilege; administrators must define roles and map them correctly. Sensitive actions (for example, deleting data, exporting transcripts, or changing enterprise-wide routing) should be limited to a small set of admin roles and reviewed periodically.

In Brilo AI, Admin role is the role that includes elevated capabilities and should be limited to trusted administrators.

Brilo AI enforces permission checks on UI actions and API calls, and audit logs capture role assignments and privilege changes. Brilo AI will block UI and API operations if the caller’s assigned permission set does not include the required capability. Brilo AI does not override external identity providers unless configured to sync roles from those systems.

Healthcare example: A hospital’s care coordination team can be assigned a role that allows them to start and stop Brilo AI voice agent campaigns and edit patient-facing scripts, while denying access to billing reports. This keeps clinical staff focused on patient workflows while protecting financial data.

Banking example: A fraud investigation team can receive a role that grants access to call transcripts and case notes but disallows changes to call routing or agent model training. The contact center operations team gets the opposite permissions so they can tune routing without accessing sensitive case files.

Insurance example: Claims adjusters can be given a role to view claim-related call recordings and submit escalation tasks, while the underwriting team keeps access to model configuration and bulk export functions separate.

Brilo AI voice agent workflows can include role-checked handoffs that route a caller to a human queue or notify a user based on their permissions. When a Brilo AI workflow triggers a human handoff, the system evaluates the recipient’s role to confirm they have permission to receive the handoff (for example, to listen to recordings or access PII). If the target user lacks the needed permission, Brilo AI can route to an alternate queue or raise an escalation task for an authorized team member.

Administrators can configure escalation policies so that only users with specific roles receive high-privilege alerts or access to sensitive transcripts. Brilo AI records the handoff and the receiving user’s role in the audit log.

If you use a CRM or an external roster, prepare a mapping between your CRM groups and Brilo AI teams.

If you plan to call webhooks for routed events, prepare your webhook endpoint.

Can I create custom roles in Brilo AI?

Yes. Administrators can create and name custom roles and explicitly choose which Brilo AI capabilities are enabled or disabled for each role.

Can permissions be assigned to individual users instead of teams?

Yes. Brilo AI supports assigning roles directly to individual users as well as to teams or groups, giving flexibility for exceptions and temporary access.

How are permission changes tracked?

Permission changes and role assignments are recorded in Brilo AI audit logs so administrators can review who changed what and when.

Can a user have multiple roles?

Yes. Brilo AI allows multiple role assignments; the user’s effective permissions are the union of assigned roles unless your policy enforces stricter conflict rules.

What happens if a user attempts an action they don’t have permission for?

Brilo AI blocks the action in the UI or API and returns an authorization error. The attempted action and the user’s role are logged for review.