Skip to content

Teams and access control

A team owns workflows and holds the plan. Everyone starts with a personal team. To work with others, invite them and give each a role.

A team of more than one needs Developer or above. Per-person sharing, cluster access, the audit log and Google sign-in need Business. Multi-factor sign-in works on every plan. See Plans and billing.

Role Can
Viewer Read workflows and runs, including logs and artifacts. Can’t change or run anything.
Editor Build, save and run workflows. Can’t delete them or manage people.
Admin Everything an Editor can, plus add and remove people, change team settings, delete workflows and approve requests.
Owner Everything an Admin can, plus manage billing and make other Owners.

Owners and Admins invite people by email from Team settings, People (/settings/people). Invites last seven days. Only an Owner can make an Owner, and the last Owner can’t be removed or demoted.

A pending invite holds a seat until it’s accepted or revoked, so an address can only have one. Resend on its row emails a new link and gives it another seven days; the link sent before stops working.

To give a person or group access to one workflow, connector or WorkflowTemplate, add them in its share dialog. Their team role doesn’t change. You need edit access to share, and they must already be in the owning team.

Level Lets them
Can view See it
Can run Start runs
Can edit Change it. Includes the other three.
Can delete Delete it

Can run doesn’t include Can view, so give both if they should see it too. Connectors and WorkflowTemplates have the same levels minus Can run.

Folders and repositories can’t be shared. A folder is only a label, so a workflow gets nothing from it. Shares and removals go in the audit log.

Members get whatever the group has and lose it when they leave. Create groups under Team settings, Groups and add people by hand, or map a Google group and let your directory handle it. Rename on a group changes its name and nothing else, including for a mapped group.

Add someone to a mapped Google group and they join the Dagweave group and the team. Remove them and they lose both, within fifteen minutes.

Syncs never touch Owners, and a mapped group can’t make anyone an Owner. The directory can’t lock you out.

Group mapping needs two things (Google sign-in works without them):

  • Your Workspace super admin grants Dagweave read-only directory access under Security, Access and data control, API controls, Manage Domain-Wide Delegation.
  • You save one of your Workspace admins’ addresses as the Directory admin under Team settings, Sign-in.

Google sign-in is a Business feature. An Owner or Admin sets it up under Team settings, Sign-in.

  1. Enter your Workspace domain and save it.
  2. Click Test with Google and sign in with an account on that domain. The test fails if the domain doesn’t match, so a typo can’t lock you out.
  3. Turn on Require Google sign-in for this team.

From then on, anyone on the team with an address on your domain has to use Google, and their passwords and GitHub sign-in are refused. Members with other addresses sign in the way they always have: the test proves you run the domain, not their accounts. Passwords aren’t deleted, so turning it off brings them back.

A group mapping can’t be edited. Delete its row and map the group again. To stop using Google sign-in altogether, click Remove Google sign-in at the bottom of the pane. Passwords and GitHub work again, the domain is free for another team to claim, and mapped groups stay but Google stops filling them.

If your team moves off Business, Google sign-in keeps working as it’s set up, including Require Google sign-in for this team. Sign-in still shows the settings, but you can’t change them or map another group. You can still remove Google sign-in.

It’s optional and per person: gear menu, Security. Use an authenticator app (TOTP), one or more passkeys (WebAuthn), or both. Setting up the app gives you ten single-use recovery codes for when you lose your device, so add one even if you mostly use passkeys. Keep the codes safe.

To turn two-factor off, enter a code from your app. If passkeys are your only second factor, Turn off two-factor removes them.

Gear menu, Security, Password. Enter your current password and a new one of at least 8 characters. Every other browser and device signed in as you is signed out; the one you’re using stays signed in. If you sign in with Google or GitHub and never had a password, use Forgot password on the sign-in screen to set one.

Cluster access controls what someone’s runs can do on your cluster. Set it per person or group in Team settings, with no Kubernetes RBAC to write:

  • Dispatch scoping limits which namespaces they can send runs to. Pick the namespace from the ones the cluster says it runs in. A namespace nobody holds a grant on can be removed from the list.
  • Run identity sets the service account their workflows run as. It can be one made for a single run and deleted with it. A draft can be edited until it’s submitted; after that, New version opens a copy to edit. Each card shows its parameters and who approved or rejected it, with their note.
  • Namespaces gives each run its own namespace, deleted afterwards along with everything the run made.

Run identity is off until whoever installs the connector turns it on and lists what it may grant. See Run identity.

The Argo controller must watch every namespace runs go to. A cluster-wide Argo install does. With a namespace-scoped install, point a controller at each group’s namespace, and skip namespace-per-run: the namespace doesn’t exist until the run starts.

An organisation is a named set of teams that list WorkflowTemplates in the marketplace for each other to install. Each team keeps its own plan and its own people, and a team is in at most one organisation.

Open Team settings, Organisation. A team owner types a name and clicks Create organisation. The team is its first member and the owner its first admin. To add a team, an admin enters its team id and clicks Invite team. The team joins when one of its owners clicks Join on the invitation.

Publishing Everyone in the organisation needs Business. Browsing and installing from the marketplace need Production. See Publish to the marketplace.

A team owner can take the team out. Its listings stop showing to the rest of the organisation, and templates other teams already installed from it stay theirs, because an install is a copy.

Open it from the gear menu, Audit log. Nobody can edit or delete entries. Reads are removed after 90 days.

Area Events
Sign-in Sign-ups, sign-ins and sign-outs, Google and GitHub sign-ins, password resets
Multi-factor Authenticator and passkey changes, step-up checks
API tokens Creating, listing, scoping, moving to a team, using and revoking tokens
Workflows Creating, editing, relabelling, upgrading, deleting, publishing and running workflows
Runs Cancelling and stopping runs, uploading run artifacts, issuing artifact download tokens
Triggers Creating, editing, deleting and firing triggers
Clusters Adding, enrolling and deleting connectors, reading connector logs
Data sources Creating, deleting, listing and reading sources
Sharing and groups Shares granted and revoked, group and membership changes
Cluster access Changes to dispatch scopes and run identities, including approvals; service accounts and namespaces created and removed for runs
Team Renaming, members and roles, invites, notification settings, GitHub App claims, usage views
Organisations Creating one, inviting a team, joining and leaving
Marketplace Installing WorkflowTemplates
Billing Plan changes, the Business trial starting and ending, and plan, quota or trial changes made by Dagweave staff
Reads Every successful read made with an API token or the MCP server, reading a step’s logs in the app, and exporting the audit log

Refused requests are logged too, as denied. Filter by action, outcome, actor, time and reads.

Click a row to open it. You get the object’s full id with a copy button, the IP and token the call came from, the event’s details, and for a denied row the reason it was refused. A workflow, run or trigger has a link to open it, and Every event about it narrows the log to that one object. Workflow events record the workflow’s name, so a deleted workflow can still be found by name.

Export CSV gives every event the filters match, not only the ones loaded on screen. Each row has the time, actor email and IP, credential or token, action, object, outcome, details as JSON, and whether it was a read.