A person presses a button in an app and a manager approves in HR
Who is involved
| Role | What they do |
|---|---|
| Insights analyst | Builds the app page and binds the button to an HR action. |
| Employee | Presses the button. |
| Manager | Approves the request from their own HR list. |
Step by step
- Insights analyst
Adds a page with a button bound to HR's create-request action for work from home.
What they see:The binding keeps the permission HR requires.
- Employee
Opens the app page and presses the button.
What they see:HR files the request under their own name and the page says what happened.
- Manager
Opens their approvals in HR.
What they see:The new request is waiting, in the normal queue.
- Manager
Approves it.
What they see:The request is marked approved by HR's own rules.
- Employee
Checks their own requests in HR.
What they see:The request shows as approved.
Who is told what
HR sends its own approval notifications. Insights adds no message of its own, only a record of who pressed. An app is visible to its builder until it is published, which opens it to the whole company, so the person pressing must be able to open the page.
Related
- Insights — Business Intelligence & Apps
- HR Management
- A ready-made report is installed once and read by people who see different numbers
- A report is shared by link with an outside auditor
- A warehouse is connected and its numbers sit beside ERP data
- A ready-made sales pipeline report
- Accounting figures feed the month-end close page
- Team workflows