TeamRetro Roles and Permissions

TeamRetro manages user permissions and roles at three levels: 

• Within each account
• Within each team
• Within each meeting (retrospective or health check)

This document summarizes what these roles represent and the permissions each have.

Account Roles

TeamRetro defines four roles at the account level - Owner, Administrator, User + Insights (enterprise only) and User. The Owner role is automatically assigned to the user who initially created the account. By default, all additional users added to an account have only the User role.

Team API keys are created in each team's settings by Team Admins or Account Administrators, once team API keys are turned on for the account.

Only the Account Owner can:

• change the account name, subdomain, logo, and branding
• manage billing, the subscription, and transactions
• create and view account-level API keys
• set up SCIM provisioning
• set allowed email domains
• set allowed IP ranges
• set a custom "Request New Team" message and URL
• delete the account
• give another user the Owner role

Account Administrators can manage everything else in Account → Settings.

Team Roles

Team Members may be assigned the additional Admin role, granting them privileges to manage membership of the team and create new meetings. Each team must have at least one admin. 

Retrospective / Health Check Roles

Retrospective / Health Check Participants may be granted the Facilitator role, giving them tools to drive the meeting activities. Each activity must have at least one Facilitator. By default, only the Team Admin who started the activity has the Facilitator + Participant role.

AI assistants

An AI assistant, whether trAI or your own assistant connected over MCP, acts as you and has exactly your permissions. Some actions are also limited to certain meeting steps. See What AI assistants can do at each meeting step.