DeployBrief DeployBrief
← Back to Documentation

Team Management

Manage your workspace's members, roles, permissions, and collaborate on deployment briefs.

Workspace Structure

DeployBrief uses an workspace-based structure where teams share connections, templates, presets, and briefs. Each workspace can have multiple members with different roles and permissions.

Note: When you first sign up, DeployBrief automatically creates a personal workspace for you. You can create additional workspaces or join existing ones via invitation.

Roles and Permissions

DeployBrief has three role levels with different capabilities:

Owner

Full administrative access to the workspace.

  • ✓ Manage workspace settings
  • ✓ Invite and remove members
  • ✓ Change member roles
  • ✓ Manage Azure DevOps connections
  • ✓ Create/edit/delete templates
  • ✓ Create/edit/delete presets
  • ✓ Generate and view all briefs
  • ✓ Manage API keys
  • ✓ Delete workspace

Admin

Manage resources but cannot modify ownership.

  • ✓ Invite members (cannot remove)
  • ✓ Manage Azure DevOps connections
  • ✓ Create/edit/delete templates
  • ✓ Create/edit/delete presets
  • ✓ Generate and view all briefs
  • ✓ Manage API keys
  • ✗ Cannot change member roles
  • ✗ Cannot remove members
  • ✗ Cannot delete workspace

Member

Standard access for daily operations.

  • ✓ View Azure DevOps connections
  • ✓ View templates and presets
  • ✓ Generate briefs from presets
  • ✓ View all briefs
  • ✗ Cannot manage connections
  • ✗ Cannot create/edit templates or presets
  • ✗ Cannot invite members
  • ✗ Cannot manage API keys

Inviting Members

Owners and Admins can invite new members to the workspace:

  1. Navigate to Settings → Team
  2. Click Invite Member
  3. Enter the member's email address
  4. Select the role: Member, Admin, or Owner
  5. Click Send Invitation

Invitation Process

  • The invited user receives an email with an invitation link
  • They must sign in with their Microsoft account
  • Upon accepting, they join the workspace with the assigned role
  • Invitations expire after 7 days

Important: The invited user must use the same email address for their Microsoft account as the invitation was sent to. Mismatches will prevent acceptance.

Resending Invitations

If an invitation expires or wasn't received:

  1. Go to Settings → Team → Pending Invitations
  2. Find the expired invitation
  3. Click Resend

Managing Members

Viewing Members

See all workspace members and their roles:

  1. Navigate to Settings → Team
  2. View the members list with names, emails, and roles
  3. See when each member joined

Changing Roles

(Owner only)

  1. Go to Settings → Team
  2. Find the member to update
  3. Click Change Role
  4. Select new role
  5. Confirm change

Removing Members

(Owner only)

  1. Go to Settings → Team
  2. Find the member to remove
  3. Click Remove
  4. Confirm removal

Warning: Removing a member immediately revokes their access to all workspace resources. They will no longer be able to view briefs, connections, or templates.

Leaving an Workspace

Members can leave workspaces they're part of:

  1. Go to Settings → Workspaces
  2. Find the workspace to leave
  3. Click Leave Workspace
  4. Confirm departure

Note: Owners cannot leave if they are the sole owner. Transfer ownership first or delete the workspace.

Managing Multiple Workspaces

Users can be members of multiple workspaces simultaneously. Use the workspace switcher to change context.

Switching Workspaces

  1. Click the workspace name in the top navigation
  2. Select the workspace from the dropdown
  3. All views update to show that workspace's resources

Creating New Workspaces

  1. Click your profile → Workspaces
  2. Click Create Workspace
  3. Enter workspace name
  4. Click Create

You become the owner of workspaces you create.

Use Case: Create separate workspaces for different clients, departments, or projects to keep resources isolated and organized.

Team Collaboration

Shared Resources

All members of an workspace share:

  • Azure DevOps Connections: Everyone uses the same PATs and connections
  • Templates: Templates are available workspace-wide
  • Presets: All members can use configured presets
  • Briefs: All generated briefs are visible to all members
  • API Keys: Shared API keys for automation

Best Practices

  • ✓ Use descriptive names: Make templates and presets clear for all team members
  • ✓ Document conventions: Establish team standards for naming and workspace
  • ✓ Assign appropriate roles: Follow principle of least privilege
  • ✓ Regular audits: Review member list and remove inactive users
  • ✓ Train new members: Ensure they understand workspace conventions

Audit Trail

DeployBrief tracks important actions for security and compliance:

  • Member invitations and removals
  • Role changes
  • Connection additions/modifications
  • Brief generation
  • Template and preset changes

View audit logs in Settings → Audit Log (Owner and Admin only).

Security Considerations

  • Principle of Least Privilege: Grant minimum necessary access. Most users should be Members.
  • Regular Reviews: Quarterly review of member list and roles to ensure accuracy.
  • Offboarding: Immediately remove members when they leave the team.
  • PAT Security: Since connections are shared, ensure PATs have minimal scopes.
  • API Key Management: Rotate API keys regularly, especially after member departures.

Next Steps