openmasu
solutions · human resources
Hire, onboard and plan time off without five scattered spreadsheets.
Track every candidate against the opening they applied for, turn a public form into new records, and keep onboarding and leave in the same base. Roles decide who can edit, and the data lives on EU servers.
- Candidate kanban linked to each opening
- Public application form, answers arrive live
- Read-only roles and data hosted in Germany
| Name | Opening | Stage | Applied | Score | |
|---|---|---|---|---|---|
| Dana Whitfield | Backend engineer | Interview | Oct 2 | 4 | [email protected] |
| Marco Lindqvist | Backend engineer | Screening | Oct 6 | 3 | [email protected] |
| Priya Raman | Product designer | Offer | Sep 24 | 5 | [email protected] |
| Tom Okafor | Support lead | Applied | Oct 14 | 0 | [email protected] |
| Lena Fischer | Product designer | Rejected | Sep 19 | 2 | [email protected] |
Everyday workflows
A hiring pipeline per opening
Keep «Openings» and «Candidates» in one base, joined by a two-way link, so each opening lists its candidates automatically. A kanban view stacks cards by «Stage»; dragging a card from Screening to Interview updates it for the whole team in real time. Interviewers leave notes as record comments and @mention the hiring manager.
Applications straight from a public form
Share a form link on your careers page with name, email, phone, a portfolio URL and the opening they want. Each answer arrives as a new candidate record, live, already in the Applied column. A grid filtered by «Applied is within the last 7 days» becomes the weekly screening list.
An onboarding checklist for every new hire
Each onboarding task is a record linked to the new hire, with a checkbox, an owner picked from a single select and a due date. A formula `DATEADD({Start date}, 7, 'days')` sets first-week deadlines, and a filter «Done is unchecked and Due is before today» shows what is slipping before the start date.
A shared time-off calendar
Leave requests hold a start and end date, a type (vacation, sick, personal) and a status. The calendar view draws each absence across its span, so team leads spot overlaps before approving. A formula `DATETIME_DIFF({End}, {Start}, 'days') + 1` shows how many days each request covers.
Careful with personal data
Give hiring managers the commenter role so they can discuss candidates without editing records, and make the wider team viewers. Per-record change history shows who changed what and when. Everything is stored on Hetzner servers in Germany, inside the EU.
Views & structure
Key views
- Hiring pipeline Cards by stage, drag to move a candidate forward.
- Application form A public link candidates fill in; each answer becomes a record.
- Time off See every absence across its dates and catch overlaps early.
- Onboarding this month Filtered checklist of open tasks, sorted by due date.
Recommended fields
- Opening (Link to another record) Ties each candidate to the role; the opening lists them back.
- Stage (Single select) Colored hiring stages that drive the kanban columns.
- Score (Rating) A quick 1–5 interviewer score you can sort by.
- Portfolio (URL) Links to the CV or portfolio wherever it's stored.
- Start date (Date) Anchors onboarding deadlines and first-week tasks.
- Days off (Formula) Length of each leave request from its start and end dates.
Your agent over MCP
Connect your own agent, like Claude or ChatGPT, over MCP. It reads and edits the base with your token's permissions, so a read-only token can answer questions without changing anything, and its edits appear live and marked in history.
query_records create_records link_records aggregate_records
Bring hiring and onboarding into one base
Start with openings and candidates, add a form, and invite your team with the right roles.