Set system and team roles/permissions

Standard

Enterprise

Within Jira Align, there are two application roles: system and team roles. This topic will help you to better understand the difference between them and what rights they have.

Team roles

Team roles have certain responsibilities, such as running standup meetings, accepting stories, or managing sprints. For example, if a story is in the backlog, anyone can work with it. However, after the sprint starts, only certain team members can make changes. The following table provides an overview of the roles with their rights and responsibilities. For a detailed comparison of the permissions associated with each role, see the Assign Team Roles article.

Role	Rights and responsibilities
Analyst	An analyst can update the sprint after it starts and manage the sprint. This role has full control of what to do with a team. Only an analyst and a product owner can accept stories.
Architect	Day-to-day activities: create tasks and stories and enter time for tasks.
Business owner	Business owners can be members of a team for visibility, but they cannot have any allocation of effort towards work. So, for a sprint, their allocation will always be 0%.
Developer	Day-to-day activities: create tasks and stories and enter time for tasks.
Documentation	Day-to-day activities: create tasks and stories and enter time for tasks.
Enterprise architect	Enterprise architects can be members of a team for visibility, but they cannot have any allocation of effort towards work. So, for a sprint, their allocation will always be 0%.
Epic owner	Epic owners can be members of a team for visibility, but they cannot have any allocation of effort towards work. So, for a sprint, their allocation will always be 0%.
Product owner	A product owner can update the sprint after it starts and manage the sprint. This role has full control of what to do with a team. Only an analyst and a product owner can accept stories.
QA lead	A QA lead can run a daily standup meeting, add stories to a sprint, and update the sprint status.
Release train engineer (RTE)	RTEs can be members of a team for visibility, but they cannot have any allocation of effort towards work. So, for a sprint, their allocation will always be 0%.
Scrum Master	A Scrum Master manages the team and the sprint. A Scrum Master can do a number of sprint management activities, such as run a daily standup meeting, add stories to a sprint, update the sprint status, add a user in the middle of the sprint, change and update capacity for users, and other. Scrum Masters can also drop stories but not change the sprint assignment when the current sprint is in progress—a Super Admin can make this change. Alternatively, a Scrum Master can drop a story, and then reassign it to the necessary sprint.
Stakeholder	A stakeholder has the visibility of the work done within the sprint. This role has no action control.
Team coach	A team coach can update the sprint after it starts and manage the sprint.
Tester	Day-to-day activities: create tasks and stories and enter time for tasks.
UX	UX designers can be members of a team for visibility, but they cannot have any allocation of effort towards work. So, for a sprint, their allocation will always be 0%.

System roles

System roles mainly control what you see: menu items, buttons, and other. The following tables list some of the available features for each system role at installation time.

Important: If a user cannot access a page and sees the You Need More Access To View This Page message, check the respective permissions for this user's role under Settings > Roles.

There are three users—Kanban User, Default, and External User—who are omitted in the tables; they have access only to the Kanban board.

Portfolio module

Area	Role
	Super Admin	PMO	Executives	Product Owners	Team Leads	Team Member
Epics	X	X	X	X	X
Personas	X	X	X	X	X	X
PI Progress Report	X	X
Work in Process Report	X	X	X	X	X	X
Investment vs. Actuals Report	X	X	X	X	X	X
Vision	X	X	X	X	X
Success Criteria	X	X	X	X	X
Kanban Boards	X	X		X	X	X
Portfolio Room	X	X	X	X	X
Themes	X	X
Value Streams	X	X

Program module

Area	Role
	Super Admin	PMO	Executives	Product Owners	Team Leads	Team Member
Roadmaps	X	X	X	X	X	X
Backlog	X	X	X	X	X	X
Risks	X	X	X	X	X	X
Dependency	X	X	X	X	X	X
Dependency Map	X	X	X	X	X	X
Features	X	X	X	X	X	X
Work Tree Report	X	X	X	X	X	X
Program Tracking Report	X	X	X	X	X	X
Forecast	X	X	X	X	X
Program Increments	X	X	X	X	X
Program Room	X	X	X	X	X
Program Objective	X	X	X	X

Team module

Area	Role
	Super Admin	PMO	Executives	Product Owners	Team Leads	Team Member
Sprint Metrics Report	X	X	X	X	X	X
Sprint Coaching Report	X	X	X	X	X	X
Detailed Sprint Progress Report	X	X	X	X	X	X
Retrospective Summary Report	X	X	X	X	X	X
Sprint capacity	X	X		X	X	X
Sprints	X	X		X	X	X
Team Room	X	X		X	X	X
Assign Tasks	X	X		X	X	X
Stories	X	X		X	X	X
Tasks	X	X		X	X	X
Acceptance Tests	X	X		X	X	X
Team Objective	X	X		X	X	X
Defects	X	X			X	X
Kanban Boards	X				X	X
Team Meetings	X				X

Integrated users

Integrated users are users created by connectors. Unless otherwise configured, integrated users are assigned the Default system role. Integrated user licenses include access to the following functionality; applying any other system role permissions to the default system role will cause the user to be counted as a full user:

Program functionality

Program board
Story maps
Features

Team functionality

Team room
Team objectives
Impediments
Team meetings (Estimation, sprint planning, daily standup, sprint review, sprint retrospective)
Backlog
Kanban boards (backlog kanban views only, not custom kanban boards)
Stories
Defects
Tasks
Teams
Sprints

Reports

Burndowns
Sprint metrics (M1)
Sprint health
Sprint coaching
Detailed sprint progress
Sprint status
Sprint capacity
Team room reports

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.

Set system and team roles/permissions

Team roles

System roles

Integrated users

Join the Atlassian Community!

Useful links

Get started