Access to a secret is decided twice: by your role for secrets in general, and by the privileges you hold on that one secret. A privilege is a right on a single secret: manage, use or destinations. Holding the role without the privilege, or the privilege without the role, is not enough.

The three privileges

The person who creates a secret, including the person who made a request for it, receives all three on it. Nobody else has any until someone with manage grants it.

Administrators and destinations

A tenant administrator can manage and use secrets they did not create: the administrator roles count as holding manage and use on every secret. They never count as holding destinations. Only the creator, or someone the creator or another manage holder has granted destinations, can approve where a secret may be sent. Granting destinations to someone else also needs destinations yourself.

Roles

Your role sets what you can do with secrets in general. Built-in roles: No built-in role below data_admin can delete a secret, so the Secrets row of the Roles matrix shows no role in its Delete column. data_admin and account_admin can delete because administrators pass every role check; a custom role can be granted Delete on secrets. The Delete button on a secret’s page is greyed out with the reason for anyone else. Fulfilling a secret request needs Secret read to open it and Secret update to submit the value, as included in data_engineer or an administrator role. The named recipient or the requester can fulfil it with the full link and these role rights; they do not need per-secret privileges. If access is insufficient, the page asks them to contact a tenant admin or the requester and shows no request details.

See your own access

The Your access panel on a secret’s page lists the privileges you hold on that secret (manage, use, destinations), each marked held or not held, with what it allows. Below it, Role rights shows which of read, create, update, delete and bind your role allows. A button is enabled only when you hold the privilege it needs and your role allows the action (bind, create, update or delete); otherwise it is greyed out with the reason beside it. Who holds what lists everyone’s access only if you hold manage. Without manage you see only your own access, and the page says that other holders are not shown.

Grant and revoke

Granting and revoking are done with dip today; the console shows who holds what but has no control for changing it.
--to is a person’s or service user’s id, such as user:<id>. dip whoami prints your own; ask a colleague to run it for theirs. --privilege is use, manage or destinations. You need manage on the secret to grant or revoke, and destinations as well to grant destinations. Revoking removes one privilege from one person.

Scopes for dip and API keys

dip and API keys also need the right scope: secrets:read to list and open request details, secrets:write to store, request, fulfil and grant, secrets:bind to bind. A scope only lets the credential ask; your role and privileges still decide.

When your tenant stops including Secrets

Taking Secrets out of a tenant stops people acquiring more: storing, generating, requesting, binding, adding destinations and granting are refused. Everything that lets you let go keeps working, in the console and with dip: listing, rotating, disabling, deleting, destroying versions, revoking access and unbinding. The Secrets entry stays in the navigation for people who can read secrets. Nothing you stored is stranded.