Agent Permission Issues
Unable to run actions, hire agents, or configure skills? Check role hierarchies and RBAC policies.
In this article you'll learn about Common permission symptoms, then explore Workspace roles vs. Skill RBAC, and finally review Resolving permission blocks.
Common permission symptoms
Permission Deniedalert when attempting to hire, pause, or configure an agent- Action buttons or skill configuration options disabled or missing from the interface
- Actions succeed for team administrators but fail for operational team members
- Agent reports
"I don't have access to this tool"during conversation
Workspace roles vs. Skill RBAC
Permission issues typically fall into one of two layers:
1. Workspace Team Member Role
Check your assigned role under Settings → Team Members:
- Admin: Full authority to hire/fire agents, manage billing, configure channels, and assign skills.
- Member: Can converse with agents, assign tasks, and upload documents to the Knowledge Base, but cannot hire or delete agents.
- Viewer: Read-only visibility into conversations, tasks, and analytics.
2. Agent Skill Capability Grants (Deny-by-Default)
Even if a skill (e.g. Google Sheets or ikas) is connected to your workspace, an agent cannot invoke its tools until an Administrator explicitly enables that capability for that agent in Agent Detail → Skills.
Resolving permission blocks
- Promote user role: If you need operational management authority, request an Administrator to elevate your role in Settings → Team.
- Enable skill grant: In Employees → Agent Detail → Skills, toggle on the specific capability needed for the agent's assignment.
- Verify channel assignment: Ensure the agent is designated as the active responder for the channel (WhatsApp, Web Chat) in Settings → Channels.

