📄️ User Secret
User secrets are private to whoever created them. Resolving one checks both the creating user and the current tenant, so the same secret name can exist independently for different people without either of them seeing the other's value.
📄️ Workspace Secret
Workspace secrets belong to a single workspace, and resolving one requires MANAGE permission on that workspace. It's the one scope where we changed the list and the form structurally. The list picks up a workspace selector in its toolbar, the create form picks up a required Workspace dropdown alongside Secret Name, Secret Type and Description, and the very same list turns up a second time inside the workspace itself, pre-filtered to that workspace.
📄️ Tenant Secret
Tenant secrets belong to the tenant and any user in that tenant can resolve them. That reach is the whole point of the scope: a metastore credential or a storage credential that every workspace legitimately needs shouldn't have to be recreated in each one, and it shouldn't be tied to the individual who happened to configure it first.
📄️ Priority
We don't rank our three secret scopes. There's no precedence order between them, and one