TimeSheets does not maintain its own user directory or its own roles. Access follows Jira, so removing somebody from a project in Jira removes their access here too, with nothing extra to remember.
1. Roles
| Role | Where it comes from | What it grants |
|---|---|---|
| Person | Any licensed user | Log their own time, book their own leave, see their own data |
| Approver | Named in Project Settings | Decide time or leave for that project |
| Project administrator | Jira project admin | Project settings, reports and approvals for that project |
| Site administrator | Jira site admin | All settings, all projects, erasure and export |
| Billing administrator | Currently the same as site administrator | Rates, invoices and every money figure |
Billing administrator is a separate check in the code even though it currently resolves to site administrator. That way introducing a distinct finance role later is one change, not thirty.
2. Project-scoped access
Nearly everything is scoped by project. You see a project's data if you can browse it in Jira and you have a reason — you logged the time, you approve for it, or you administer it.
Requesting data for a project outside your scope is refused rather than silently returning nothing, so a report is never quietly narrower than you believe it to be.
3. Rules that have no exceptions
- Nobody approves their own time or leave — including site administrators.
- A delegate can never approve more than the person who delegated to them.
- Nobody sees their own billing rate in their own timesheet.
- An entry on an issued invoice cannot be edited by anyone until that invoice is voided.
4. Enforcement is on the server
Every check described here runs on the server. The interface hides what you cannot use as a convenience, but hiding a button is not a permission — calling the API directly gets the same refusal.
5. Scopes the app requests
The Jira permissions TimeSheets asks for, and why each one is needed, are listed in Privacy & Data Handling.
6. Where your data lives
Everything is stored in Atlassian's own Forge infrastructure. The only outbound traffic is email. Full detail in Privacy & Data Handling.