Organisation settings

This page is for org admins. Select Settings under your organisation’s name in the sidebar to open Organisation Settings. The General and Leave & Calendar tabs each have one Save Settings, and nothing on them changes until you press it, apart from the logo, which saves on its own.

General

Organisation Logo

Shown in the sidebar, on everyone’s Settings > Organisation, and to anyone signing up with your invite link. It saves as soon as you choose it, cropped square. Most images work, including photos straight from an iPhone.

Organisation Name

Renaming your organisation doesn’t change its code or invite link.

Organisation Code and Invite Link

Team members enter the code when they sign up, or follow the link, which fills it in for them. The code is your organisation’s name plus six random characters, and it can’t be changed. It’s safe to share, because everyone who joins this way waits for you to approve them. See Team members and invites.

Working Hours

Start, Morning ends, Afternoon starts and Finish, set to 09:00, 12:00, 12:00 and 17:00 to begin with. They decide what a half day is, and what a few hours off costs. Each time has to come after the one before it, though the afternoon can start the moment the morning ends. A gap between them is lunch, and costs nothing.

Changing them doesn’t recount leave that’s already booked.

How far staff may shift their own hours Pro

How far team members can move their own start and finish in their working week: Any hours they like, Locked to the hours above (the default), or Within 1 hour up to Within 4 hours. It only shows on Pro, where the working week is. When hours are locked, the working week says so before anyone tries to change them, and they can still choose where they work. Each end is checked on its own, so an hour either way means starting up to an hour earlier or later, and finishing up to an hour earlier or later.

Allowed Email Domain

One domain, like example.co.uk, which has to match exactly. Only team members with an address there can join with your code or link, and they confirm that address before their request reaches you. It doesn’t apply to team members you add yourself. Leave it blank to let anyone ask to join.

Two-factor Authentication

Require two-factor authentication makes everyone sign in with a code from an authenticator app. It applies straight away: anyone without it, you included, has to set it up before they can carry on. Set yours up first under Settings > Security. See Security.

Leave & Calendar

Leave Year

The month your leave year starts. Allowances reset on their own at the start of each year. Changing the month re-sorts everyone’s leave into the new years straight away.

How far ahead the team can book

Current leave year only, Current + next leave year (the default), Current + next 2 leave years, Current + next 3 leave years or No limit. It’s counted in whole leave years, not months. Managers booking for someone aren’t held to it.

Working Days

Include bank holidays as working days, off to start, so bank holidays don’t come off anyone’s allowance. Changing it doesn’t recount leave that’s already booked.

Which days of the week someone works, weekends included, is set on their profile under Working Days. Without any set, it’s Monday to Friday, so tick Saturday or Sunday for anyone who works them.

Calendar Visibility

Whose leave team members can see: Everyone in the organisation, Only their own team role, or Only their own leave. Managers always see everyone.

It covers the team calendar (birthdays and anniversaries on it included), calendar feeds, who else is off in a request, and Folke in Slack. It doesn’t change the Moments page or the rota: birthdays and work anniversaries are the whole organisation’s to celebrate, and anyone can hide their own birthday. With Only their own team role, someone with no team role sees only their own leave.

Carry Over

Let unused days carry over into the next leave year, with an optional Maximum and Expires after. See Carry over.

Editing Requests

Let staff edit a pending request is off to start. Turn it on and choose For how long after sending they can, from 1 hour to 30 days. Once a request is decided, or the time is up, it can’t be edited.

Max Concurrent Off

A limit on how many team members can be off at once, as a number of Team members or a % of team. It’s a warning, not a rule: requests still go through, and whoever approves sees the days over the limit, so nobody is denied a break by a number. It’s counted per leave type, from approved leave, so three team members off sick doesn’t count against a holiday. Blank or 0 means no limit. Team roles can have their own limit.

Request Chart

How much a request shows either side of its dates, from 1 week either side (the default) to 4 weeks either side. See What a request shows you.

Leave Types

Which kinds of leave your team can book, with each one’s allowance and notice. See Leave types and allowances.

The other tabs

• Bank Holidays: see Bank holidays.
• Import Leave: see Importing leave.
• Team Roles: see Team roles.

Tabs on Pro Pro

These only appear when your plan includes them.

• Rota: see Setting up the rota.
• Integrations: see Slack.
• API: see the API guide.