Absence: Leave approved in one click.
And everyone sees their own balance.
An employee requests time off, an approver decides in one click and the approved absence appears in the team calendar straight away — and at the end of the month the payroll summary is ready.
Runs in your Microsoft 365 — no foreign cloud, no extra passwords.
Three steps anyone can manage.
The whole process fits in one paragraph — and your people will find it just as easy.
-
The employee requests time off
Picks the type and dates — a half day too, or a time from–to for a doctor's visit. The app counts working days without weekends and public holidays.
The balance shows on the overview straight away -
The approver decides
Approvers get an e-mail about the new request and decide from the queue in one click. A rejection always carries a reason.
The requester gets the outcome by e-mail -
The team and payroll stay informed
The approved absence is in the team calendar straight away. At the end of the month an administrator downloads the payroll summary as a CSV.
Sensitive types only as “Absence”
What it looks like in practice
Balances on the overview, a new leave request with an instant summary of days, the team calendar and approving a request with one click.
Today vs. with Absence
This is how it looks in many companies for as long as leave runs through e-mail and a spreadsheet.
30 minutes on screen, no company presentation
- 5 minHow people ask for time off today and who approves what
- 10 minA request, balances and the team calendar through an employee's eyes
- 10 minApprovals, entitlements and the payroll summary through a manager's and HR's eyes
- 5 minWhat a rollout would mean for you + pricing
Time-off requests
A link straight to a new request
Balances and editing requests
One-click approvals
Team calendar
Sensitive types protected in the data
Private requests
Entitlements and people
Payroll summary
Absence types, holidays and roles
Teams and phone
Your data stays with you
Requests, entitlements, absence types, holidays and the team calendar live in SharePoint lists on the app's site inside your Microsoft 365, under your identities and permissions. The app has no server or database of its own and uses no AI.
Requests private in the data too
The request list has item-level permissions: an ordinary employee can reach only their own requests in SharePoint, approvers and administrators can reach all of them. This is not hiding in the app — someone else's request is out of reach even with a direct link.
Sensitive reasons masked on write
For types marked as sensitive the shared team calendar gets only a neutral “Absence” entry. The real type is not there at all, so it cannot be found even by querying outside the app. The note on a request never reaches the calendar, e-mails or the payroll summary.
Only administrators change the setup
Absence types, holidays and annual entitlements are protected by SharePoint permissions — only the app's administrator group can write them, while everyone who uses the app can read them. The app's settings are protected the same way.
No new passwords
People sign in with their company Microsoft account, and e-mails go out through Microsoft 365 from the account of whoever took the action. When someone leaves, IT handles it in one step — blocking the account removes access to the app too.
Only the licence request reaches us
The app downloads the file with your company identifier and expiry date and checks it in your browser. The app sends us no requests, names or reasons for absence; the app code, fonts and release notes load from our content delivery network. A bug report or suggestion reaches us by e-mail only when a user sends it.
Monthly licence by company size
The subscription is based on the total number of internal users in your Microsoft 365. Within a given size you get the full scope of the app, with no surcharges for individual features.
Implementation
The app creates its lists, role groups and the permissions on the request list by itself the first time a site administrator opens it. Together with you we then set up absence types, public holidays, annual entitlements, approvers and roles — and you are ready to go.
A site administrator to open the app for the first time, and a one-off approval of the app's Microsoft Graph permissions in the SharePoint admin centre — the app requests them all at once. Without them it sends no e-mails and does not recognise roles given to Entra ID groups. A group is notified only at its own e-mail address, and annual entitlements are entered for people added to a role individually.
Support rate
Consultancy, environment changes, training or user support beyond the licence.
Support is charged per each started 15 minutes of work. We always tell you the expected scope up front.
Does the app calculate the statutory leave entitlement?
Will colleagues see that I'm at the doctor's or off sick?
Who approves a request?
How do absences get into payroll?
How long can one request be?
Does the app put leave into Outlook?
Does it work in Teams and on a phone?
Where is our data stored?
Is the interface in English?
What does deployment involve and what does implementation cost?
How do app updates work?
Goes well with Absence
Further reading on the blog
Need help putting your SharePoint in order first? Explore our audit, governance and care services
What exactly do you want to discuss?
Pick what's burning most right now. We'll get back to you, walk through your situation and propose next steps, including an indicative price.