You connect the capabilities
Think of permissions as cables connecting an employee to tools and actions. Leave a capability disconnected, authorise it or require a human decision. Some actions offer more detail than a simple on/off switch, but the metaphor helps explain control.
Instructions and skills describe how to work. Permissions authorise what the employee can execute. An imported skill, external message or another employee's collaboration does not itself grant account access or permission to send or publish.
The three states
- Deny: the action is not authorised for this employee.
- Ask for my approval: the task prepares a request whose scope you review and decide on.
- Allow without asking: the action may run within current access, capabilities and limits.
Configure and check
Open the employee's Permissions and autonomy. Review the autonomy profile and individual capabilities. For applications, distinguish a permitted capability from a specific connection. Configure Gmail, Outlook and IMAP per mailbox under Edit profile → Email mailboxes. The president can save permission changes.
For an approval request, review its content, resource and recipient. For email, choose Send or Do not send; Request changes can revise the draft where available. Decide each request on its actual content.
Begin with approval for steps you are still learning to delegate. After reviewing repeated results, decide which actions to authorise. You expand autonomy deliberately for each responsibility.