Team and Members

Team is a collaborative unit in Braidrun - several people maintain the same workflow, share credentials, and approve each other. This page explains how to build a team, invite members, and migrate resources.

A Picture to Understand the Structure

• An account can belong to Multiple Team; pull down in the upper right corner of the UI to switch the current Team.
• Each Team has its own:
  • Workflow List
  • Template/module library (modules promoted by yourself are shared with the team)
  • Credentials Namespace
  • Scheduling/Webhooks
  • Member list and permissions
  • Execution history + audit log
  • Notification Settings
  • Subscriptions and quotas

Create a Team

1. Navigate to "Team" on the left → "New Team" in the upper right corner.
2. Fill in the name (other members will see it), slug (part of the URL), and description.
3. Select a package - choose from the packages purchased by the current account, or click "Upgrade Package" to buy one first.
4. The creator automatically becomes the Team Owner.

Invite Members (Email Invitation, Starting from 2026-04-27)

Starting from 2026-04, inviting members is entirely via email instead of UUID pasting:

1. Team details page → Member tab → "Send invitation"
2. Enter their email address (one at a time; idempotent — resending to the same address reuses the pending invitation record)
3. The system sends an email containing a link to a 32-byte random token (256 bits entropy, non-enumerable)
4. The other party clicks the link → jump to the /teams/invitations/accept redemption page
5. If the other party is not logged in, it will automatically jump to the login page. After logging in, return to the redemption page.
6. System verification during redemption: the currently logged in user's email address must be consistent with the invitation email address (case-insensitive) - the forwarded link cannot be used by others.

Create an Invitation Using the API

curl -X POST 'https://braidrun.com/api/teams/{teamId}/invitations' \
  -H 'Authorization: Bearer dyk_...' \
  -H 'Content-Type: application/json' \
  -d '{"email": "newmember@example.com"}'

Exchange on the other side:

curl -X POST 'https://braidrun.com/api/teams/invitations/accept' \
  -H 'Authorization: Bearer dyk_...' \
  -H 'Content-Type: application/json' \
  -d '{"token": "<32-byte-token-from-email>"}'

Member standing

A team has only two standings, owner and member; the fine-grained "who can edit, who can only look" is controlled through workflow sharing permissions — see Permissions & Sharing.

Member Management

What the owner can do in the member list:

• see each member's display name and email, and who created the team;
• send and revoke invitations;
• remove a member — their past activity records stay, but their access to team resources ends immediately.

Members can leave a team on their own; the owner does not need to act.

What to do when the sole owner wants to leave

There is currently no self-serve transfer of ownership: a team's owner is whoever created it, and the API only offers renaming, deleting the team and adding or removing members. So when the sole owner leaves, the options are:

1. have the successor create a new team, move the workflows across with "move to team", and recreate the credentials under the new team;
2. once nothing is left behind, the original owner dissolves the old team;
3. and when a subscription or seat allocation is involved, check with platform support first on how the billing follows.

Switch Current Team

Pull down the user's avatar in the upper right corner → select "Current Team". After switching:

• All sidebar lists (Workflow/Credentials/Scheduling/Execution/Approvals) are reloaded to the new team's data
• The URL will carry a team parameter, which will be retained after refreshing.
• Switching will close the workflow editor you have opened (to prevent cross-team accidental changes)

Movement of Resources Across Teams

Workflow Moved to Another Team

1. Workflow details page → Settings → "Move to Team".
2. Choose the target team — you need to be a member of it.
3. The system verifies whether the credentials referenced in the workflow also exist in the target team with the same name - if they do not exist, they will be listed and you can choose to "skip/create credentials with the same name/cancel move".
4. After confirmation the workflow + historical execution are migrated together to the new team.

Cross-Team Replication Of Credentials

Credentials cannot be "moved", only "copied" - to avoid accidentally revoking the original team's permissions. You will be asked to re-enter the values and then create a credential with the same name to the target team.

Audit records

Changes to workflows, credentials, schedules, approvals and membership all leave audit events on the platform side. The default retention is 180 days hot and 730 days archived; the actual values are set by the deployment.

Mind the viewer, though: ordinary teams have no audit-log page — that capability is opened on the Enterprise plan. To trace changes inside a team, start with the workflow version history, which records the author of every save.

Disband The Team

Only the owner can dissolve a team, and the deletion takes effect immediately: the team record goes first, then its pending invitations are cleaned up. The platform does not export anything for you, and there is no grace period afterwards.

Next

• Permissions & Sharing — The full comparison of the three layers: account role, team identity, and workflow share permissions
• Subscriptions and Pricing — Quota differences for Team/Enterprise
• Credentials — Semantics of team-shared credentials