This article is for Timesheets for Data Center. Visit Cloud
Permissions Overview
The tables below list the following types of permissions and roles:
Some important Jira permissions that Tempo relies upon.
Tempo administrative and user permissions.
Tempo roles, such as Team Lead and Account Lead, which already include certain permissions.
Important
For Tempo users with Approve Timesheets permissions, you must also have View All Worklogs permissions on the projects you are reviewing in order to see the worklogs of other users.
For Jira users to be able to access and use Tempo Timesheets, they must have the Work On Issues permission for at least one Jira project. See the Project permissions and roles table below.
For Jira users to be able to log time in Tempo Timesheets, Time tracking must be ON in Jira.
On this page:
Global Permissions
Permission | Description | Notes | Who can give permission by default | Configuration location |
---|---|---|---|---|
Permission to:
| All Jira users in your organization are granted access by default. This permission can can be useful if there are users in your organization who may need to view tasks in Jira, but who are not required to log time. This permission does not restrict developers from using the Tempo REST APIs according to their permissions. | Jira Administrators | Jira administration at the top-right > System > SECURITY Global permissions | |
Grant or deny access to Tempo Planner to specific groups in your organization, or to external Jira users with permission to view your Jira issues. | All Jira users in your organization are granted access by default. | |||
Tempo Budgets Access | Grant or deny access to Tempo Budgets to specific groups in your organization, or to external Jira users with permission to view your Jira issues. | All Jira users in your organization are granted access by default. | ||
| By default, Jira Administrators are not granted Tempo Rate Administrators permission (see below). However, Jira Administrators can grant themselves any type of Tempo administrative or user permission that they do not already have. | |||
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
| |||
Permission to:
|
| |||
Permission to:
|
| |||
Permission to:
|
| |||
Permission to:
| Price rates are used for revenue reports and billing. |
Project Permissions and Roles
Permission | Description | Notes | Who can give permission role by default | Configuration location |
---|---|---|---|---|
Administer Projects | Within the context of a project, permission to edit:
| Jira Administrators | Jira administration at the top-right > Projects > project name > Permissions | |
Within the context of a project, permission to:
| ||||
| Troubleshooting tips
| |||
Within the context of a project, permission to view all worklogs | Troubleshooting tip A possible reason why worklogs are not viewable is that users do not also have Browse Projects permission (see above). | |||
Within the context of a project, permission to log work on behalf of other Jira users who have permission to log time for the project | ||||
Within the context of a project, permission to delete all worklogs made on issues. | ||||
Within the context of a project, permission to delete own worklogs made on issues. | ||||
Within the context of a project, permission to edit all worklogs made on issues. | ||||
Within the context of a project, permission to edit own made on issues. | ||||
Set Billable Hours | Within the context of a project, permission to set billable hours of worklogs for the project in Tempo. | |||
View Issue Hours | Ability to access the total number of hours per issue, but not to see individual worklogs. |
Team Permissions and Roles
Permission | Description | Notes | Who can give permission or role by default | Configuration location |
---|---|---|---|---|
Tempo Team Administrator | 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. | You can specify a Team Lead when you create a team: Teams  > Create Team or by configuring basic team information: Teams  > team name > Team Lead | |
Permission to view all worklogs for all team members. | Teams > team name >  at the top-right > Permissions | |||
Can manage worklogs, i.e. create, edit, and delete team member worklogs. Users with this permission can make changes to worklogs in user timesheets after the scheduler has closed the timesheet period. | ||||
Permission to approve timesheets, i.e. review, approve, and reject team member timesheets. | ||||
Permission to view time planned for team members. | ||||
Permission to manage plans, i.e. create, edit, and delete team member plans. | ||||
Permission to approve plans, i.e. review, approve, and reject team member plans. | ||||
Permission to manage a team, i.e. add members, edit team settings, and manage team permissions. Users with this permission can make changes to worklogs in user timesheets after the scheduler has closed the timesheet period. | ||||
Permission to view a team and its members. This permission is always granted to all permission roles for the team. |
Customer and Account Permissions and Roles
Permission or role | Description | Notes | Who can give permission or role by default | Configuration location |
---|---|---|---|---|
Tempo Account Administrators | See the Global Permissions table above. |
| ||
Tempo Rate Administrators | See the Global Permissions table above. |
| ||
| Account Leads must be Jira users, but are not required to be Tempo Timesheets users. |
| You can specify an Account Lead when you create an account or when you edit the account information: Accounts  > account name > People Involved > Lead | |
Permission to view the account revenue report and the time and expenses report for accounts that are associated with a customer. | Account Leads are automatically granted the Browse Customer Revenue permission for all customers. | Accounts  > Customers >  at the top-right > Permissions |