Approvers and permissions
Calibro Track has three roles and no permission scheme of its own. What you can see follows what you can already see in Jira.
Roles
Assigning approvers
Go to Settings → Approvers. Approvers are set per project. A project can have several — any one of them can decide, and the entry disappears from the others’ queues once decided. One person can approve for as many projects as you like.
Time submitted against it has nobody who can decide on it, so it sits as Submitted indefinitely and the submitter can’t edit it — they’d have to recall it first. Settings flags this with the number of entries affected. Assign someone, and the queue clears itself.
What’s in Settings
Settings is organised by who a change lands on, not by topic. Every pane carries a badge saying which — Just you or Affects everyone · admin — so you never have to guess whether you are about to change your own view or the team’s. There are four groups:
- Your preferences
- Week starts on, date format, show durations as, your weekly target, and whether a running timer shows in your browser tab title. Yours alone.
- Team defaults
- Admin only. The default weekly target, the submission period, whether approved time locks, whether a description is required on every entry, and what happens to logged time when Jira moves or deletes its issue.
- Timer
- Admin only, and three things: when a running timer starts asking questions, when it stops itself, and whether people can pause one. See Timing your work.
- Approvers
- Admin only. Who can decide on time, per project.
There is a search box above the list. It matches the settings themselves, not just their headings, so looking for “description” finds the one in Team defaults without you having to know it lives there.
Team defaults
- Default weekly target
- The hours a week everyone starts on. People can override it for themselves in Your preferences.
- Submission period
- Weekly or bi-weekly — the unit that Submit and the approvals queue work in.
- Lock time once approved
- Whether an approved entry can be changed at all without an approver reopening it.
- Require a description
- Blocks Log time when the description is empty. Off by default — turn it on when the notes are going to a client rather than to a colleague.
- When an issue moves to another project
- Where its logged time goes. All its time follows (the default) re-routes every entry to the new project’s approver and reports it there. Approved time stays put moves only what is still undecided, so hours already approved — and perhaps already paid — stay under the project they were approved in. The issue key is updated either way.
- When an issue is deleted
- What happens to time logged against it. Keep and mark its time (the default) leaves every entry in place with a Deleted issue mark. Remove unsubmitted time deletes drafts and rejected entries on the issue; anything submitted or approved is kept and marked, because an approver has seen it and a payroll export may reference it. See Submitting and approvals for what people see.
Your own preferences
The Your preferences section only affects you — week start, date format, duration format, your weekly target, and whether a running timer appears in your browser tab title. Changing them never affects anyone else’s view.
Week start and date format start out matching your Jira language settings, so for most people there’s nothing to change.