Workspace Administration
Locations, holidays & currencies
Maintain locations, holiday calendars, and currencies used across ERP modules.
Locations, holidays & currencies
Locations, holidays & currencies covers shared regional settings for locations, holiday calendars, default currency, timezone, date format, and operational reporting. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.
What this surface is
- Primary purpose: shared regional settings for locations, holiday calendars, default currency, timezone, date format, and operational reporting.
- Where users start: Locations are managed at
/global-settings/company/locations; holidays are managed at/global-settings/holidays. - Where administrators configure it: Default currency, language, timezone, date format, and time format are configured in
/global-settings/company/settings. - Runtime/detail surface: These settings appear in schedules, attendance, finance, billing, inventory, reporting, and user profiles.
- Platform connections: Regional setup connects company settings, teams, users, schedules, holidays, currency displays, and reports.
Where it lives
| Area | Path or surface | Use it for |
|---|---|---|
| User surface | Locations are managed at /global-settings/company/locations; holidays are managed at /global-settings/holidays. | Day-to-day work and review. |
| Configuration | Default currency, language, timezone, date format, and time format are configured in /global-settings/company/settings. | Setup, permissions, routing, labels, and behaviour. |
| Runtime/detail | These settings appear in schedules, attendance, finance, billing, inventory, reporting, and user profiles. | Testing the live experience users actually see. |
Configure it
- Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
- Open the owning product route: Locations are managed at
/global-settings/company/locations; holidays are managed at/global-settings/holidays. - Review the configuration route and permissions before changing live behaviour: Default currency, language, timezone, date format, and time format are configured in
/global-settings/company/settings. - Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
- Configure Location, Holiday, and Currency first because they shape the rest of the rollout.
- Add Timezone and Date/time format only after the core path works with sample data.
- Test the runtime surface as a restricted user, not only as a superadmin: These settings appear in schedules, attendance, finance, billing, inventory, reporting, and user profiles.
- Check downstream connections after saving: Regional setup connects company settings, teams, users, schedules, holidays, currency displays, and reports.
- Record the owner, rollout date, and support path for the configuration.
- Review the first week of activity and remove any option that users do not understand or need.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| Location | Work, people, stores, or assets are tied to a site | Route: /global-settings/company/locations. |
| Holiday | Schedules must account for non-working days | Route: /global-settings/holidays. |
| Currency | Money values need a tenant default | Set in Company Settings. |
| Timezone | Dates and schedules need consistent display | Set in Company Settings. |
| Date/time format | Users need local formatting | Set in General Settings. |
| Regional reporting | Managers compare locations | Use reports and dashboard filters. |
Operating notes
- Keep labels aligned with the words users see in the product, especially Location and Holiday.
- Permissions still matter even when a menu, page, or link is visible.
- If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
- If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
- Use reports or logs to confirm the change produced the expected operational result.
- Capture configuration decisions in rollout notes so support teams know what changed.
- Do not reuse one option for unrelated processes just because it is already configured.
- Review linked notifications, workflows, dashboards, and reports after changing this surface.
- Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
- When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
- Keep retired settings hidden or archived so users do not choose outdated paths.
- Assign an owner for ongoing review; unattended configuration becomes stale quickly.
For developers
Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.