Your people and availability.Organised your way.
Ready-to-use software connects employees, working calendars and leave requests. Work with Shappy to adapt the information, views and approval process to your own organisation.
Decide a request with the allowance and schedule in view.
Sarah prepares leave decisions. She checks available days, working calendars and overlapping requests.
- 01
Find the employee
The record links the employee, existing account, team and working calendar.
- 02
Check the request
Requested days are checked against a manual allowance and planned absences.
- 03
Keep the decision
HR approves or refuses; cancellations retain a reason. Managers follow availability.
Read availability with its context.
Directory, requests, allowances and HR documents belong to the same fictional example. Actual documents are restricted to HR.
Decide with the dates in view.
Sarah, the HR manager, reviews whole days and a fictional overlap before simulating a decision.
An HR review that fits your team.
Tell Shappy what needs to change. Watch your software take on your way of working.
Your software, your rules
Add a team view of pending requests, with balances and planned absences. Add a coordination note visible only to HR.
Watch the transformation
Take this example for a spin.
Switch views, open a record and try the available actions. Linked records show how the workflow fits together.
Share only the information needed.
Leave relevant to planning does not require sharing an entire employee record. Access rights are part of setup.
- Google Calendar
Read selected calendars and events.
What is needed : After an explicit click, personal connection and Core permissions. The described scope creates no event and does not synchronise leave.
- Gmail
Check the connected personal account profile.
What is needed : Explicit profile read only. No HR message reads, sending or synchronisation within this scope.
- Payroll, projects or reporting
Information to select according to role and intended use.
What is needed : Connections to define and validate separately: permissions, published fields and formats. No statutory payroll export or automatic cross-application sharing is delivered.
Choose a team and two leave requests.
- 01
Prepare calendars
Define teams, existing accounts, working weeks and non-working dates.
- 02
Walk through a decision
Check one eligible request and one conflicting with allowance or dates.
- 03
Check your organisation
HR decides and managers coordinate. Define the views and responsibilities to adapt with Shappy, then check access for each role.
Your questions before choosing your software.
Can we adapt the software to our organisation?
Yes. Employee and leave tracking provide the starting point. Work with Shappy to evolve the fields, views and responsibilities specific to your company. Access and approval processes are checked before use; any change to leave calculations requires separate validation.
Does the software calculate payroll or statutory leave?
No. Allowances are entered manually. No payroll, statutory accrual or national compliance is claimed.
Can employees request half days?
The current scope covers whole days and separate requests for each year. Working calendars and non-working dates provide the calculation context.
Who approves and who sees documents?
HR decides leave requests; managers coordinate the schedule. Records retain document references, but file transfers are disabled until the RootCX access update. Enabling them does not create separate file permissions for each employee.
Is the external calendar changed?
Not in the described scope. Google Calendar can be read after an explicit click, personal connection and authorisation; no external creation or synchronisation is claimed.
Software that reflects your organisation.
A team, an allowance and two requests: start with a concrete workflow, then adapt the information and responsibilities specific to you.
Bring a representative record and your working rules. We will define data migration and the first changes to check.