Granting permission to users

Jira Administrators permission

Permission to:

• Perform most Jira administrator tasks
• Perform most Tempo administrator tasks

• Tempo Team Administrators permission (see below)
• Tempo Account Administrators permission (see below)

Jira Administrators can grant themselves any Tempo administration or user permission that they do not already have.

Jira Administrators

Permission to:

• Grant or deny access to specific groups in your organization.
• Grant or deny access to external Jira users with permission to view your Jira issues.

All Jira users in your organization are granted access by default. This permission can be useful if there are users in your organization who may need to view tasks in Jira, but who are not required to plan time.

This permission does not restrict developers from using the Tempo REST APIs.

Browse Users permission

Permission to view lists of Jira user names and group names and to select users or groups from the lists.

Many users might require this permission.

Examples

• Tempo Team Administrators (see below) require Browse Users permission so that they can add members to teams.
• Many users might require Browse Users permission so that they can reassign issues to other users.

Tempo Team Administrators permission

• Permission to create, configure, browse, and delete teams and to manage team permissions
• Browse Team permission (see below) for all teams
• Plan Time permission (see below) in Tempo Planner for all teams
• Permission to create, configure, browse, and delete programs. (A program is a group of teams that are associated with the same Jira project or the same Jira Agile board.)

• Tempo Team Administrators can grant themselves Approve Timesheet permission (see below).
• Tempo Team Administrators permission is not sufficient for moving employees between different types of working week or sets of public holidays.
• By default, Jira Administrators receive Tempo Team Administrators permission

Tempo Account Administrators permission

Permission to create, configure, import, export, and delete accounts

• Only Jira Administrators can configure the following account settings:

  • Whether the account value is cleared when issues are moved between projects
  • An alternative name for the account field
  • Whether an account value is required or optional in a field configuration
• By default, Jira Administrators receive Tempo Account Administrators permission

Within the context of a project, permission to edit:

• Project role membership
• Project components
• Project versions
• Some project details

Jira Administrators

Projects > View All Projects > project name > Project Administration > Permissions

Within the context of a project, permission to:

• Browse the project
• Use the issue navigator
• View individual issues

• Browse Team permission (see below) for the team that you lead
• Plan Time permission (see below) for the team that you lead
• Permission to configure your team

Tempo Team Administrators

You can specify a Team Lead when you create a team:

Tempo > TEAMS more > Create New Team

or by configuring basic team information:

Tempo > TEAMS more > team name > Configuration > Configure > Team Lead

• A high-level overview of the capacity and progress of the teams in a program
• The ability to plan epics and product releases for the teams

• A program is a group of teams that are associated with the same Jira project or the same Jira Agile board.

• To create a program or to plan iterations for teams from the program level, Tempo Team Administrators permission is required (see above).

Tempo > TEAMS more > Manage > Programs

• Team Leads
• Tempo Team Administrators

By default, Team Members are given the role name Member. However, you can give customized role names, such as Developer, Tester, or Scrum Master, to Team Members.

When you customize role names, the permission that the Team Members have does not change.

Permission to:

• See the team's information
  
• See planned time for each member of the team
  
• Select this team on forms that contain a Team field (for example, the Team field in an issue)
  
• See this team in the program that contains the team
  

All Team Members automatically receive Browse Team permission for their own teams.

Tempo > TEAMS more > team name > Configuration > Permissions

• Permission to plan time for team members to work on projects, project versions, project components, and issues
• If Jira software or Jira Agile is installed, permission to plan time for team members to work on sprints
• Permission to plan work on the team backlog
• Permission to plan time on projects

• Team Leads (see above) automatically receive Plan Time permission for their own teams.
• Tempo Team Administrators (see above) automatically receive Plan Time permission in Tempo Planner for all teams

Responsibility for the account

• Tempo Account Administrators
• Jira Administrators

You can specify an Account Lead when you create an account:

Tempo > ACCOUNTS more > Create Account

or by configuring basic account information:

Tempo > ACCOUNTS more > account name > Configuration > General > Lead