Skip to main content
Version: 1.0.8

Team Management

Manage your organization's users, roles, and access permissions.

SettingsTeamManagement

User Management​

Viewing Team Members​

Navigate to Platform › Settings › Team Management. The page has two tabs, Users and Teams.

The Users tab lists members in a Team Members table:

ColumnDescription
MemberAvatar, full name and account email
Org. RoleThe user's organization role, as a badge
ProjectsThe projects (workspaces) the user can reach
StatusActive, Inactive or Pending Verification
ActionsRow menu, hidden from regular users

A search box filters by user, a Projects dropdown narrows to one project, and Member, Org. Role and Status are sortable.

Adding Users​

  1. Click Add Team Member
  2. Enter the Email (the form tells you whether the address already belongs to a user)
  3. Pick a Role — the list is your company's real roles, standard and custom
  4. For a new user, fill in Full Name, and optionally Job Title and Phone
  5. Save

User Status​

StatusDescription
ActiveVerified and able to sign in
Pending VerificationAdded, but has not yet verified their email and set a password
InactiveDeactivated — cannot sign in, data preserved

Managing Users​

The row menu on a member offers:

ActionEffect
Activate / Deactivate UserToggles whether the user can sign in. Needs organization:user:update.
Change RoleReassigns the organization role, with a confirmation step. Needs organization:user:update.
View Login HistoryOpens the user's login history
Remove from OrganizationDeletes the membership, after confirmation. Needs organization:user:delete.

The Owner cannot be acted on at all. A Lead may only remove regular users, never another Lead or an Admin.

Role Management​

Default Roles​

The built-in roles, highest first:

RoleNotes
OwnerThe organization's founder. Shown as a badge, never assignable, and never actionable from Team Management.
Account Admin
Admin
Lead
UserThe default role for a new member
Viewer
Dealer

Anything else is a custom role created in Role Management, and is styled as such wherever roles appear.

Creating Custom Roles​

  1. Navigate to Settings › Role Management (needs organization:role:read)
  2. Click Create Role (needs organization:role:create)
  3. Enter a role name — it is required before the role can be saved
  4. Tick the permissions it grants
  5. Create Role

Default roles cannot be edited or deleted. Their row menu offers View Permissions to inspect them, and Copy to New Role to start a custom role from the same permission set.

Permission Categories​

Module Access​

Control access to modules:

Module access is granted per workspace, not per user — see Workspaces. A user reaches a module when their workspace has it enabled and their role carries the matching permission.

Feature Permissions​

A permission key is written module:resource:action. The role editor lays them out as a matrix — one row per resource, one column per action:

  • View — read
  • Create — create
  • Update — update
  • Delete — delete
  • Archive — archive, only shown when some permission actually uses it

Permissions that are not CRUD get their own labelled row instead of a column — for example autorunner:testdata:reveal, analyzer:pbi:generate and smartrequest:request:approve.

Clicking a column header selects or clears that action for every row shown, and a module filter narrows the matrix to one product at a time.

Platform Permissions​

The organization:* keys cover the platform surfaces:

  • organization:user:* — user management
  • organization:role:* — role management
  • organization:team:* — teams
  • organization:workspace:* — projects (workspaces)
  • organization:billing:read and organization:billing:request — billing
  • organization:company:* — organization settings, one key per tab
  • organization:provisioning:* — Provisioning

Integration permissions live under integration:* — integration:tracker:read is labelled "View integrations".

Editing Roles​

  1. Open a custom role's row menu and choose Edit Role & Permissions
  2. Modify the permission matrix
  3. Save Changes
caution

Modifying roles affects all users with that role.

Team Organization​

Team Structure​

A team is a flat group of members that carries project access together. There is no team-lead field — seniority is the member's own organization role.

Each team row expands to its members, showing Member, User Role, Recent activity and Status.

Creating Teams​

  1. Open the Teams tab of Team Management
  2. Click Create Team (needs organization:team:create)
  3. Enter a Name — required — and an optional Description
  4. Save, then add members to the team

A search box filters teams by name and description.

Team Settings​

The point of a team is shared project access: open a team's projects drawer and switch on each project (workspace) the whole team may reach. Access then follows team membership as people join and leave.

Access Audit​

Login History​

Each member's row menu has View Login History, which opens that user's sign-in record.

Best Practices​

Role Design​

  • Keep roles simple and clear
  • Use least-privilege principle
  • Review roles quarterly
  • Document role purposes

User Onboarding​

  1. Create account
  2. Assign appropriate role
  3. Add to relevant team
  4. Send welcome documentation
  5. Schedule training

User Offboarding​

  1. Deactivate the account immediately
  2. Review their login history
  3. Remove them from teams
  4. Remove them from the organization once nothing depends on the membership

Regular Maintenance​

  • Monthly: Review inactive users
  • Quarterly: Audit role permissions
  • Annually: Full access review