permission.proto

path mgmt/v1alpha1/permission.proto

package mgmt.v1alpha1

---

Messages

ProcedurePermissions

What a scoped API key must be granted to call a procedure.

Name	Type	Description
all_of	repeated Permission	The key needs every one of these.
none	bool	The procedure needs no permission: it tells the caller about itself, or about the deployment, and holds nothing a scope restricts. Set only when that is true — a procedure with neither this nor a permission is refused to every scoped key.

---

Enums

Permission

A permission a caller can be granted: one action on one kind of entity, as the RBAC names them. An API key's scope is a list of these, and can only narrow what the key may do.

Name	Number	Description
PERMISSION_UNSPECIFIED	0
PERMISSION_ACCOUNT_VIEW	1
PERMISSION_ACCOUNT_EDIT	2
PERMISSION_ACCOUNT_CREATE	3
PERMISSION_ACCOUNT_DELETE	4
PERMISSION_CONNECTION_VIEW	5
PERMISSION_CONNECTION_VIEW_SENSITIVE	6	Holding a connection's secrets: seeing them in clear, and using the connection — reading its schema, scanning or previewing its data — which takes them. Without it, a connection comes back masked, and cannot be connected to.
PERMISSION_CONNECTION_CREATE	7
PERMISSION_CONNECTION_EDIT	8
PERMISSION_CONNECTION_DELETE	9
PERMISSION_JOB_VIEW	10
PERMISSION_JOB_CREATE	11
PERMISSION_JOB_EDIT	12
PERMISSION_JOB_EXECUTE	13	Running a job, which writes to a real destination — and anything that makes it run: creating it with a first run or an active schedule, setting its schedule, resuming it, writing or enabling one of its SQL hooks.
PERMISSION_JOB_DELETE	14

---