Organization settings
Organization settings, under Settings → Administration → Organization, holds the foundational details that shape how Flowtly looks and behaves for everyone in your company.
Company identity
- Short name and logo used across the app and on documents.
You can set the logo by uploading an image file or by entering its web address in Logo URL. An address must start with https:// and point at a publicly reachable website. An http:// address, or one on a private or internal network, is refused when you save it, with the message The logo address must be a public https:// web address.
A logo stored with an http:// address is fetched over https:// from the same host, so it still appears on invoice and timesheet PDFs. This works only when the site serves the image over https://; if it does not, or if the address names an explicit port such as http://example.com:80/, no logo is shown. In that case upload the image file or replace the address with an https:// one.
Localisation and formats
- Company default currency for new records.
- UI language and legal language (the language used for generated legal documents). UI language is the fallback for people, not an override: anyone who picks a language in Profile → Language keeps it, and someone who never has sees Flowtly in their browser's language. The organisation's UI language is what a new person sees when their browser asks for a language Flowtly does not yet speak.
- Date format and amount format so numbers and dates display the way your team expects. The available date formats, and what an organisation that has never chosen one now sees, are set out under Date format below.
- Billing period format — how a billing month reads on an invoice line built from an invoice line template, such as
07/2026. A billing period covers a month and has no day, which is why it is set apart from the date format. - Organization calendar type.
Operating basics
- Company working days: the days of the week that feed time tracking and schedules.
- Company start date.
Date format
Dates display in one of four formats. Pick the one your team reads most naturally:
| Setting | 5 August 2026 reads as |
|---|---|
dd.MM.yyyy |
05.08.2026 |
dd/MM/yyyy |
05/08/2026 |
yyyy-MM-dd |
2026-08-05 |
MM/dd/yyyy |
08/05/2026 |
If your organization has never chosen a date format, it now uses dd.MM.yyyy — so 5 August 2026 reads as 05.08.2026. This is the default day-first order most Flowtly customers pick when they do choose, which is why it is the one applied when nobody has.
If you have already chosen a format, nothing changes. Your setting is untouched and continues to apply. The default only ever governs organisations that have no date format of their own.
Changing it affects how dates display everywhere in the app, for everyone in the organisation, and takes effect as soon as it is saved. It changes presentation only — no date you have entered is altered.
These values apply organisation-wide, so it is worth setting them correctly during initial setup — see Set up your organisation.
Notifications
Pause notifications until…, admin-only. Set a future date and time and the organisation's create-path notifications go quiet until then — mail, in-app bell and push, for:
- Leave (time off) requests
- Absences
- Contracts
Everything else keeps sending as normal: invoices, password resets and other account emails are never paused.
While a pause is active, the page shows Notifications are paused until <date> — so a pause set for a bulk import or a migration cannot be mistaken for a working notification system. Click Resume now to clear it immediately, or let it expire on its own at the date and time you chose.
The same banner appears on the pages where absences are managed — People → Time off and Settings → People → Absence notifications — so an administrator does not have to know where this control lives to notice a pause. There it offers Resume now and Pause settings, which brings you back here.
Only an administrator can set or clear this — the control is hidden from everyone else. The pause itself still applies organisation-wide: it mutes what every employee, manager and approver would otherwise be notified about.
Example use cases
- Setting the default currency and date format when onboarding a new company.
- Uploading a logo so it appears on generated documents.
- Replacing an
http://logo address with anhttps://one, or uploading the image file, when the logo does not show on PDFs. - Pausing notifications while a bulk import of leave requests or contracts runs, then resuming once it settles.