Skip to main content

Workflow permissions

What you can do with a workflow depends on two things: the access you hold (read or write) and where you hold it (the whole organization, or an account, namespace, or application). That lets a team own its automations without seeing or touching the rest of the organization.

Variables and secrets follow a stricter rule, because workflows of every team can read the ones on the organization and on folders.

Read and write access​

Write access comes with the Ops or Admin role.

ReadWrite
See workflows in the list and open them in the editorYesYes
See their runs in Executions and follow them step by stepYesYes
Create, edit, save, move, rename, and delete workflowsNoYes
Publish, unpublish, and manage aliasesNoYes
Run, cancel, re-run, and send signalsNoYes

With read access only, the editor opens read-only.

Where your access applies​

Every workflow has an Owner: the organization, or an account, namespace, or application. Access on the organization covers every workflow. Access on an account, namespace, or application covers the workflows owned there and below it.

For example, with the Ops role on the payments namespace you see and edit the workflows owned by payments and its applications, and nothing else. When you create a workflow, pick that namespace (or one of its applications) as the Owner: creating it at the organization level is denied.

Variables and secrets​

Variables and secrets live on three levels, and who can read or change them depends on the level:

LevelWhich workflows read itSee the entrySee a variable's valueCreate, edit, or delete
OrganizationEvery workflowRead access anywhereRead access on the organizationWrite access on the organization
FolderWorkflows in the folder and below itRead access anywhereRead access on the organizationWrite access on the organization
WorkflowOnly that workflowRead access on the workflowRead access on the workflowWrite access on the workflow

Organization and folder entries reach workflows of every namespace, so only someone with access to the whole organization can change them. A team with access to one namespace keeps its own values on its workflows.

A secret's value is never shown to anyone, whatever their access: it can only be replaced.

Folders that hold variables or secrets​

A workflow inherits the entries of its folder and of every folder above it. So creating a workflow in a folder that holds variables or secrets, or below one, or moving a workflow there, needs write access on the organization. Otherwise it's denied, and the error names the folder.

The root folder (/) doesn't count: every workflow inherits the organization entries wherever it sits.

What you see with access below the organization​

With access on an account, namespace, or application, the Variables and secrets page shows:

  • Every organization and folder entry, plus the entries of the workflows you can read.
  • No value for organization and folder variables. Selecting one says you need access to the whole organization to see it.
  • In Used by, only your workflows: None of yours or 2 of yours. Workflows in other namespaces may use the entry too.
  • In Add, only the workflows you can edit as the place for a new entry.

Across workflows, people show as Unknown user when you can't read the organization's users, so you see that someone changed an entry or a workflow, but not who.

Check your access through the API​

GET /workflows/grants tells you where you hold an action: all: true for the whole organization, or the list of NRNs below it.

curl -L 'https://api.nullplatform.com/workflows/grants?action=write' \
-H 'Authorization: Bearer <token>'
{ "all": false, "nrns": ["organization=1:account=2:namespace=3"] }

Each row of List all secrets and variables also carries permissions.canWrite and permissions.canReadValue, so a script knows what it can do with each entry without trying.

Next steps​