Permissions, approvals and connected apps

Understand delegated access, human decisions and connected-app permissions.

A connection grants access to an eligible workspace under your own authority. It does not approve every future external action or give an automated client the right to make human decisions.

Overview

The external client acts with your enrolled identity and existing workspace permissions. Connected app suggestions, catalog listings and saved logins are not proof that an account is connected, authorized for this Artisan, or ready for a specific provider action.

Use the normal dashboard's Apps and decision flow to connect accounts and approve requested actions. Provider failures, expired credentials and unavailable capabilities need their actual recovery; they do not mean the same approved payload needs a new approval merely because execution failed.

MCP and delegated CLI clients cannot approve an action on your behalf. Review and decide pending approvals in the Needs you dock in Artie. Connecting a client does not approve every future action.

Disconnect an unwanted client in Artie’s connection settings. Signing out of the delegated CLI clears local credentials but does not revoke the standing workspace connection. Cancel already accepted tasks separately if you no longer want them to run.