Organization settings

Organization settings define shared business defaults used by employee, attendance, leave and other workflows. Review the effect on those workflows before saving. These settings are separate from your browser's appearance preferences and workspace sign-in security.

Access needed

Access depends on your assigned permissions and workflow scope.

Read the shared settings, work calendar and holidays: organization.read
Reading does not grant policy changes.
Role and permission labels
Typical responsibility: Authorized organization reader. Role names alone do not grant access.
Read organization settings and structure
Save defaults, restore overrides or change calendars/holidays: organization.settings.manage
The interface also reads the catalogue with organization.read. Department/position management does not substitute for settings management; source workflows retain independent rules.
Role and permission labels
Typical responsibility: Authorized organization settings administrator. Role names alone do not grant access.
Manage workspace settings, calendar and holidays

Demo screenshots may show broader access than your account.

Open the shared defaults

Open Organization → Organization settings. Use General for the settings catalogue, Work calendar for effective working weeks and Holidays for non-working dates.

Organization settings General tab and regional preferences — Demo shared settings; no policy or calendar changes were made.

Each setting shows its effective value and a Default reference. A workspace override replaces that default; restoring the default removes the override. The demo values illustrate the interface and are not a recommended policy for every organization.

Review regional preferences

Setting	What to consider
Time zone	Shared timing and overdue calculations can depend on it. Choose the organization's intended timezone, not simply your browser's location.
Language and date format	Review the selected locale and format examples before saving.
Currency	A default is not an instruction to convert existing compensation or payroll records. Check each record's own currency.
Default phone country	Helps interpret numbers stored without an international country code; it does not repair every invalid destination.

Update a setting

Find the relevant policy
Read the setting's description, current value and default. Identify which module uses it and review that workflow's guide before changing it.
Prepare the intended values
Change only the necessary fields. Respect the choices and validation shown by the form, and review every pending change before saving.
Save and verify
Select Save changes. Read any error, then reload the settings and confirm each intended value. Do not assume a failed save left all values unchanged.
Check the affected workflow
Open the relevant attendance, leave or employee screen and verify how the new default is used. Existing records can have their own captured values or workflow state; a settings save is not a bulk recalculation.

Other services receive setting-change updates and are documented to keep cached copies for at most one minute. This is a settings propagation window, not a promise that payroll, leave accrual or another background process completes within one minute.

Review employment and attendance policies

Shared organization employment and attendance policy fields — Demo shared settings; no policy or calendar changes were made.

The catalogue includes overtime thresholds, week start, rest between shifts, late allowance, shift scheduling, probation and notice defaults, leave approval steps and leave-year start. Read each field's help rather than treating a zero value as the same rule everywhere.

First day of the week sets timesheet and shift-week boundaries; it does not choose working days. Work calendar determines the working week. Payroll's overtime multiplier, standard monthly hours and partial-period proration have their own calculation consequences: see Payroll Settings.

For leave balance timing, see Leave balances and policies. Changing the leave-year start or approval configuration is not a manual balance adjustment.

Review the work calendar

The Work calendar tab shows the working week for the current date and lets you preview a date or compare effective versions. With no saved versions, the demo uses the default Monday–Friday week.

Work calendar showing default weekdays and date preview — Demo shared settings; no policy or calendar changes were made.

Each calendar version applies from its effective date until the next version begins. Working-week previews are before holidays. Today’s summary uses the server's UTC date, as the screen explains; a selected preview date is used as written.

See Holidays for the existing holiday instructions rather than duplicating holiday records here.

Treat retention as a data-lifecycle decision

Data retention fields cover records such as inbox notifications, delivery history and completed tasks. Review the period and affected record type before saving. Shortening retention can make older eligible records subject to cleanup; lengthening it does not recover records already removed.

Retaining duplicate-message checks and sent system messages has a different purpose from keeping a user's inbox. Follow your organization's approved retention policy rather than applying one duration indiscriminately to every field.

Restore a default carefully

When a setting has an override, use its offered reset/default action and review the confirmation's setting name and default value. Confirm only the intended reset, then verify the effective value. This is a saved removal of the override, not a reset of all settings or a reversal of downstream work.

Troubleshooting

Problem	What to check
Settings can be read but not saved	Read and settings-management permissions are separate.
A saved setting appears delayed elsewhere	Allow for the documented cache window, refresh and inspect the source workflow.
A calculation did not change	Existing records may capture settings; review that module's recalculation rules.
Week start changed but working days did not	Week boundary and effective work calendar are separate settings.
Reset produces an unexpected value	Read the displayed default before confirming; removing an override restores that default.
Old records remain missing after increasing retention	Longer retention does not recover deleted records.

What was verified

The live General catalogue and Work calendar were inspected in light theme. Three screenshots reuse the shared viewer. No setting, calendar version, retention period or approval rule changed. Propagation timing and downstream recalculation were not live-tested.