OAuth permissions
Permissions are named OAuth scopes. A scope is necessary but never sufficient by itself: Stenz still checks subscription, connection policy, resource ownership, risk level, and current product state.
Read, write, and special scopes
Section titled “Read, write, and special scopes”:readscopes allow bounded reads in one studio.:writescopes allow changes in that domain; client-visible writes still require confirmation.clients:piireveals eligible client contact fields and is separate from ordinary client reads.media:readpermits eligible media access and does not make client content trusted.deposits:refundandinvoices:issuecover high-risk actions that still require a recent approval inside Stenz.offline_accessallows renewable authorization until the connection is paused, revoked, or otherwise invalidated.
Grant the smallest useful set, then reconnect or run consent again when you intentionally add a scope. Removing a scope can make a tool disappear without deleting the underlying studio data.