App template · Internal ops
Employee Requests
Add to workspaceLeave, letters and equipment, asked for in one place, each with the approval it needs behind it, and a balance that says what is left.
What arrives
One click puts all of it in your workspace, wired together. Rename anything afterwards — the pages, boards and Flows read the columns, not a copy of them.
- 4
- Tables
- 7
- Pages
- 3
- Forms
- 7
- Sidebar entries
Employee Requests
Records
Leave requestsLetter requestsEquipment requestsInsight
DashboardEmployee Requests
Ask for something
Leave, a letter, or a piece of equipment. Each one goes to the right person on its own; follow it below once it is in.
The tables
Equipment Requests
One row per thing somebody asked for, the approval it needed, and where the order got to.
- Order Status
- Status
- Submitted by
- Submitted at
- What do you need?
- Why
- and 3 more
Leave Balances
What each person is allowed this year, what they have used, and what is left.
- Employeelinks
- Year
- Allowance (days)
- Taken (days)
- Remainingcalculated
- Notes
Leave Requests
One row per leave request, from the form to the decision.
- Leave Type
- Status
- Submitted by
- Submitted at
- Working Days Requested
- First Day of Leave
- and 3 more
Letter Requests
One row per letter somebody asked HR for, and the letter itself once it is written.
- Letter
- Status
- Submitted by
- Submitted at
- Addressed To
- Needed By
- and 3 more
What people open
- PageLeave balancesAllowance and days taken this year, per person. HR updates Taken as leave is approved; Remaining works itself out.
- Record page{{$row.item}}
- BoardEquipmentEvery order IT has placed, by where it got to. The Flow stops at Ordered; drag a card to move it on.
- Request portalEmployee Requests
- Record pageLeave: {{$row.leave_type}}
- Record pageLetter for {{$row.addressed_to}}
- DashboardEmployee requests dashboard
What runs
Each of these is a Form and the Flow behind it. Steps wait for a person; Rules decide which person, on what the row says.
Equipment Request
Someone submits the formAnything under $500 goes straight to IT to order. Anything at $500 or above waits for the person's manager first. Either way IT places the order and the board takes it from there.
2 Steps · 1 Rule · ends on Ordered and Rejected
Leave Request
Someone submits the formLeave approvals where the length of the absence decides how many sign-offs it needs.
2 Steps · 1 Rule · ends on Leave Approved and Leave Rejected
Letter Request
Someone submits the formSomebody asks HR for an employment letter, a salary certificate or a visa support letter. HR writes it and attaches it to the request.
1 Step · ends on Letter Delivered
Before you add it
This app shares your workspace's Employees table rather than making a second copy of it. If you have one with name and email, it is used; if you do not, it is created for you.
What it is
The three things people ask HR for most, in one app, with one front door.
Leave goes to HR and, if it is long enough, to a director. A letter goes to HR to write. Equipment goes to IT to order, after a manager if it costs enough. The person asking opens the same page for all three, and follows their own requests underneath it without emailing anyone.
What you get
One portal, three Forms. Leave request, letter request, equipment request, on the home page as a catalog. Everyone in the workspace can submit; each one routes itself to the right people; the requester sees *Being reviewed*, *With the director*, *Being prepared* or *Being ordered* in their own list.
Leave that knows when it needs a second signature. HR checks the request against the cover arrangement. A Rule reads the number of working days: five or more goes to the department director as well, anything shorter is confirmed on HR's decision alone. HR can escalate a short one by hand.
Letters with the letter on them. Employment letter, salary certificate or visa support letter. HR gets a task with a 72-hour clock, writes it, attaches it, and the request closes on *Delivered* with the file on the record.
Equipment that only bothers a manager when it should. Under $500 goes straight to IT. $500 and above waits for the requester's manager first. IT records the order reference, the Flow stops at *Ordered*, and the Equipment board carries the order to *Delivered* by hand, exactly the way the Purchasing app's orders board does.
A balances table. Allowance and days taken per person for the year, with *Remaining* working itself out. It links to the same Employees table your other apps use.
A dashboard. What is open in each of the three, leave by type, leave by status, and the days taken this year.
The pattern worth stealing
Three Flows, one app, one home page. A request app does not need a Flow per page or a page per Flow: the catalog lists whatever Forms the app has, the requester's list shows whatever they submitted, and a Form published next month appears on both without anyone editing a page.
Who uses this
- HR teams running leave, letters and kit for a company
- Office managers who are also the IT desk
- People operations at a school or a charity
What it expects from your workspace
A shared Employees table, so a leave balance belongs to the same person your asset register already knows. If your workspace has one, this app uses it; if not, it is created for you. Four reviewers arrive as placeholders you map before publishing: HR, the Department Director, Line Managers and IT. The $500 equipment limit and the five-day leave threshold are numbers in a Rule, not code.
Arrives with its tables, pages and Flows, running in your workspace.
Add to workspace