Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The tables below list the following types of permissions and roles:

  • Some important JIRA important Jira permissions that Tempo Planner relies uponon
  • Tempo administrative access, administrator and user permissions
  • Tempo roles, such as Team Lead, which already include are assigned certain permissions by default


Panel
borderColor#60c1ef
titleColor#ffffff
titleBGColor#60c1ef
titleOn this page
Table of Contents
maxLevel2
minLevel2


Global permissions

JIRA

Permission

What you get by default


Notes

Who can give permission by default
Configuration location

JIRA Administrators Jira Administrators permission

Permission to:

  • Perform most JIRA administrative most Jira administrator tasks
  • Perform most Tempo administrative administrator tasks
  • Tempo Team Administrators permission (see below)
  • Tempo Account Administrators permission (see below)

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

Jira Administrators

Administration cogwheel Image Modified > System > SECURITY Global Permissions

Tempo Planner Access permission

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 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 same Jira project or the same JIRA 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  Jira Administrators receive Tempo Team Administrators permission

Tempo Account Administrators permission

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

  • Only JIRA 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  Jira Administrators receive Tempo Account Administrators permission

Project permissions


Permission

What you get by default


Notes

Who can give permission by default
Configuration location
Administer Projects permission

Within the context of a project, permission to edit:

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

JIRA AdministratorsJira Administrators

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

 
Browse Projects permission

Within the context of a project, permission to:

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

Team permissions and roles


Permission or role

What you get by default

Notes
Who can give permission or role by default
Configuration location
Tempo Team Administrators permissionSee the 'Global permissions' table above.


Team Lead role
  • 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
The Team Lead role is not sufficient for moving employees between workload or holiday schemes or for changing the Team Lead.

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 moreteam name > Configuration > Configure > Team Lead

Program Manager role
  • 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 same Jira project or the same JIRA 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 Member roleBrowse Team permission for your team (see below)
  • Team Leads
  • Tempo Team Administrators

Tempo > TEAMS more > team name > Configuration > Members

Tip
iconfalse

Alternative method:

Tempo > TEAMS more > team name > Planning > Add member to team


Customized roles, such as Developer, Tester, or Scrum MasterSee notes >

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.

  • JIRA Administrators Jira Administrators can create customized role names:
        
    Administration
    cogwheel > Add-ons > TEMPO TEAMS Tempo Roles
        
  • Team Leads and Tempo Team Administrators can assign role names to Team Members when they add or configure Team Members:
          
    Tempo > TEAMS more > team name > Configuration > Members
Browse Team permission

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

Plan Time permission
  • Permission to plan time for team members to work on projects, project versions, project components, and issues
  • If JIRA If Jira software or JIRA 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

Account permissions and roles


Permission or role

What you get by default

Notes
Who can give permission or role by default
Configuration location
Tempo Account Administrators permissionSee the 'Global permissions' as shown in the table above.


Account Lead role

Responsibility for the account

Account Leads are not required to be users of JIRA Jira and Tempo Planner users.
  • Tempo Account AdministratorsJIRA 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