Timeaway settings glossary
Short definitions for panels under Settings. Jira site admins manage the Jira lead group. Members of that group (and site admins) configure org-wide leave types, holidays, and policies. Team leads manage Timeaway teams and rosters.
- Team Leads group
- Jira group whose members can change global Timeaway settings and create teams. Reuse Workpulse Team Leads if it exists. Creating the Jira group, ensuring it exists, and adding or removing members is site-admin only — the Team Leads group panel in Settings is not shown to regular leads.
- Team
- Named roster in Timeaway (not a Jira group) with one or more leads and members. Drives calendar, heatmap, and on-call scope. Leads assigned on a team can edit that team even if they are not in the global Jira lead group.
- On-call enabled
- Per-team flag that turns on weekly on-call scheduling and handoff requests.
- Leave type
- PTO, sick, unpaid, etc. — color, paid flag, and whether balances apply.
- Allotment
- Yearly earned hours per person or policy bucket; supports accrual and carryover.
- Prime buckets
- Group allotments by role or region when hours differ by cohort.
- Holiday set
- Non-working dates by region — excluded from working-day math on requests.
- Policy
- Rules such as notice period, max consecutive days, or blackout windows.
- Blackout dates
- Org-wide no-request windows (e.g. release freeze).
- Delegated approvers
- Backup approvers when the primary lead is out.
- Coverage defaults
- Org defaults for hours per day, default region, and notification behavior.
- Availability feed
- Published snapshot for Capacita or other TimeSuite apps that read headcount.
- ICS export
- Subscribe to approved leave in Outlook, Google Calendar, or Apple Calendar.
- Slack webhook
- Post request / approval events to a channel.
- Confluence archive
- Optional page archive when requests are approved (audit trail outside Jira).