# Permission setting best practices

> Recommendations for configuring Delegate and Cartographer permissions securely, by role — individual users, IT administrators, and developers creating skills.

## For individual users

To configure Delegate and Cartographer securely as an individual user, take the following steps:

1. Start with [Cautious mode](local-security-configuration.md#approval-mode) until you understand what the agent does.
2. Enable only the [tool categories](security-settings.md#tool-permissions) you need — if you don't use command execution, disable it.
3. Review [tool permissions](security-settings.md#tool-permissions) after installing new skills — skills may request additional capabilities.
4. Use [Protected files](security-settings.md#protected-files) and [Blocked apps/sites](security-settings.md#ui-automation) for sensitive directories and destinations (tax documents, medical records, etc.).
5. Set [Screen context](local-security-configuration.md#screen-context) to **None** when working with confidential visual information.
6. Pin important sessions so you can review what the agent did later.

## For IT administrators

Deploying and enforcing these settings centrally, across all users, is covered in [Governance with Automation Ops](centralized-configuration.md), including the recommended baseline for regulated environments.

## For developers creating skills

To develop skills that follow good permission-setting practices, take the following steps:

1. Request only the permissions you need — don't ask for [UI automation](security-settings.md#ui-automation) if your skill only reads files.
2. Document required permissions clearly in your skill description. See [Sharing skills with your team](share-skills-with-your-team.md).
3. Handle permission denials gracefully — explain to users why a permission is needed.
4. Test in all three [Approval mode](local-security-configuration.md#approval-mode) settings to ensure your skill behaves appropriately.
5. Don't rely on being able to reach a site the user or organization has blocked — [blocked websites](security-settings.md#ui-automation) are configured specifically to keep the agent out.