Understand access, permissions and approvals
Separate what Artie can read from permission to carry out an action.
Access, action permission and a specific approval answer different questions. A connection supplies an account; its permissions constrain use; your request and any required approval authorize the actual action.
On this page
Review the account and action settings
Where offered, supported action policies include Off, Ask and Allowed. Review their account and resource scope. Allowed is still bounded by your authority and current instructions; it is not permission to act in any account for any audience.
Give permission through the right owner
An authorized admin manages company access. Each owner manages personal account access. A role, skill, account connection or past successful action does not independently grant broader permissions.
Let the request guide the approval
Artie considers the actual request when deciding whether to act, show a prepared action or ask a clarifying question. Not every write needs a new card, and explicit ask-each-time preferences still apply. An approval binds the proposed action rather than creating standing permission.
Change access when the job changes
If the work needs another account, resource, audience or spending limit, make that change deliberately. A disconnected app or provider error is a capability problem; it does not by itself mean you need to give the same approval again.