Understanding Different Team Roles and Their Permissions

Team roles determine what someone can do inside a specific team workspace. Each team role provides a different level of access and responsibility, and users can hold different roles in different teams. 

These roles are different from user roles, which define what someone can access across the entire server. User roles affect organization-level permissions, while team roles only control what someone can do inside the team they belong to. Below are the roles you’ll encounter within a team and what each one can do.

Team Admin

Team Admins have the highest level of control within a team workspace. They can manage members, change roles, configure team settings, and manage all assets, data, and operations inside the team.

Server Admins added to a team are automatically assigned this role. 

Creator

Creators work with the structure and organization of the team’s content. They can create new assets, edit, and structure existing ones. Creators can’t take action on assets inside the team, such as approving a workflow, or view Submission Data. They also aren’t able to manage team members or change team-level settings.

Data Collaborator

Data Collaborators work directly with the team’s submission data.  They can view, add, edit, and comment on Submission Data in the Inbox or Submission Table. However, they can’t edit assets, such as Forms or an AI Agent, edit or manage the team and team members, or take action outside of the submission data. 

Data Viewer

Data Viewers have read-only access to Submission Data. They can view live assets and submission data, but cannot make changes to data, edit assets such as Forms, or manage the team.

How These Roles Work Together

Each role focuses on a different area of the workspace:

• Team Admin: Manages Team Members, Team Settings, and all assets.
• Creator: Creates, Manages and structures the assets themselves
• Data Collaborator:  Can view and edit submission data inside assets.
• Data Viewer: Can only view assets and submission data.

This separation ensures that team members only receive the access they need. The full list of permissions for each role is shown in the chart below.