Most of what makes TimeSheets behave differently for one team lives here. Open it from the project, or from Admin Settings if you administer several.
1. Approval requirements
Two independent switches: whether worklogs need approval, and whether leave does. A project can require one and not the other.
Turning worklog approval off means entries on that project are final as soon as they are saved — and, if billing is configured, priced at that moment.
2. Approvers
Name the people or groups who can decide, separately for worklogs and leave. Project administrators and site administrators can always decide as well. See Approvals.
3. Cost centres
Assign the cost centres that may be used on this project. A project with none cannot have time logged to it at all.
4. Weekly billable cap
An optional ceiling on billable hours per person per week for this project. Saving time above it is refused, on the server as well as in the browser.
It applies to billable cost centres only — internal work does not consume it.
5. Billing client
Attach the project to a client so its work can be invoiced. Optional; a project with no client is still tracked and reported on.
6. Overrides
A project can override some site-wide settings, such as leave auto-decision. Whether overrides are permitted at all is itself a site setting, so an administrator can keep the configuration uniform if they prefer.
7. Teams, important dates and quick events
Name teams for the team browser and bind an Atlassian group to each one — the group's members become the team. This is optional: with no team set up, the browser falls back to whoever has logged time on the project recently, so it is useful before anybody configures anything. Set a team up when you want the list chosen deliberately rather than derived.
Also record dates that matter to the project — a release, a client workshop — so they show on people's calendars alongside their own work.
