Granting permission to users
Global permissions
Permission | What you get by default |
| Who can give permission by default | Configuration location |
---|---|---|---|---|
Jira Administrators permission | Permission to:
| Jira Administrators can grant themselves any Tempo administration or user permission that they do not already have. | Jira Administrators | Administration cogwheel > System > SECURITY Global Permissions |
Tempo Planner Access permission | Permission to:
| 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 permission |
|
| ||
Tempo Account Administrators permission | Permission to create, configure, import, export, and delete accounts |
|
Project permissions
Permission | What you get by default |
| Who can give permission by default | Configuration location |
---|---|---|---|---|
Administer Projects permission | Within the context of a project, permission to edit:
| Jira Administrators | Projects > View All Projects > project name > Project Administration > Permissions | |
Browse Projects permission | Within the context of a project, permission to:
|
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 permission | See the 'Global permissions' table above. | |||
Team Lead role |
| 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 more > team name > Configuration > Configure > Team Lead |
Program Manager role |
|
| Tempo > TEAMS more > Manage > Programs | |
Team Member role | Browse Team permission for your team (see below) |
| Tempo > TEAMS more > team name > Configuration > Members | |
Customized roles, such as Developer, Tester, or Scrum Master | See 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. |
| |
Browse Team permission | Permission to:
| All Team Members automatically receive Browse Team permission for their own teams. | Tempo > TEAMS more > team name > Configuration > Permissions | |
Plan Time permission |
|
|
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 permission | See the 'Global permissions' as shown in the table above. | |||
Account Lead role | Responsibility for the account | Account Leads are not required to be Jira and Tempo Planner users. |
| 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 |
Tempo Timesheets for Server Documentation
For the newest version of Tempo Planner documentation, please visit our Help Center. For support, see our Support Portal.