One sentence instead of a project
An employee directory sounds simple until permissions come in. Who may see salaries? What does a manager see of their own team, and of other teams? This is exactly where shared spreadsheets and quickly built tools fall apart.
A fictional example you may know from our homepage: Lisa is head of HR at Wagner GmbH. She needs a directory of everyone, with team, role, start date and salary, and a reminder before a probation period ends.
Describe
Lisa writes in her own words what she needs:
"An employee directory. Only HR sees salaries, managers see their own team. I want a reminder before probation ends."
A build agent builds the app from that. Lisa writes no code, files no IT ticket and hires no agency. The result is real software with a data model, permissions and tests, not a form.
Answer the domain questions
Openbase.one only asks Lisa what she has to decide as the expert:
- "Does a contract end automatically after probation?" Lisa: "No, only after notice."
- "How many days before probation ends should the reminder come?"
How the data is stored and how the permissions are implemented is not something Lisa needs to know.
Checked before it goes live
Every version is built and checked before it goes live:
- Data model checked
- Access rules checked
- Salaries classified as sensitive, contact details as personal
- Test as a manager: no salary visible
- Test as HR: all salaries visible
For this, every page is opened in a real browser as every test persona. Only when every check passes is the directory published for Wagner GmbH. If a check fails, the version doesn't go live.
Live, with the same permissions everywhere
The directory runs in the workspace, isolated and without network access. Every access is checked against workspace, app and permissions. That includes the personal assistant: it works with the permissions of whoever is asking. A manager who asks about salaries sees none. When Lisa asks her assistant to make Tom team lead from Monday, it brings her the change for approval.
The directory also runs natively in the app for iPhone and Android, from the same code and the same data.
Change it later
Lisa wants to add a field for location? She describes it, and the new version goes through the same check. Every version is kept, and the previous one is live again in one click. The audit log shows who changed what. Code and data belong to the company: a git repository in the workspace, data exportable.
Safe means checked, isolated and reversible. Whether the probation rules are right in substance is HR's call. A support contract helps, and can include a review before going live.
What it costs
Openbase.one is priced per workspace, not per person, with unlimited users and apps. Details on the pricing page.
Describe your first app and watch it go live, checked.
Start for free