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. Fill in the other party's email address (one at a time; idempotent: resending to the same email address will reuse the PENDING invitation record) + select the pre-assigned role
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>"}'

Role Assignment

Four roles, from high to low: Owner/Admin/Editor/Viewer. See what each role can do specifically. Permissions and Roles.

Member Management

In the member list, Admin and above can:

• Modify member role (downgrade/promote)
• Remove a member (all related operation history of the other party is retained, but the permissions become invalid)
• View the last active time of each member
• Look at the number of credentials held by each member and the number of workflows created

Transfer Ownership

A team can only have one Owner. Want to transfer ownership to someone else:

1. Team Settings → "Transfer Ownership".
2. Select a current Admin as the new Owner.
3. Two-factor authentication - requires the current owner to confirm twice by email or TOTP.
4. After completion, the current Owner will be automatically downgraded to Admin; the subscription bill ownership will also be transferred.

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. Select the target team - you must be Editor or above of the target team.
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.

Team Audit

"Team Settings → Audit Log" records all changes:

• Who / when / which workflow / which field was changed
• Who / when / created / deleted / updated which credential
• Who / when / initiated / approved which approval
• Member joining/exiting/role change

Audit logs are retained for 365 days (Team)/permanently (Enterprise) and support CSV export.

Disband The Team

Owner can be dissolved. Before disbanding, the system will let you:

1. Export all workflows (ZIP of YAML)
2. Export all execution records (CSV or JSON)
3. Notify all members (automatically send email)
4. Two-factor confirmation

It can be restored within 30 days after disbandment; after 30 days, the data will be completely cleared and cannot be retrieved.

Next

• Permissions and Roles — Detailed comparison table of what the four roles can do
• Subscriptions and Pricing — Quota differences for Team/Enterprise
• Credentials — Semantics of team-shared credentials