Approvals
Some things nobody should decide alone: a large order, blocking a customer, going public. Request decisions here, approve or reject — and every decision remains on record: who, when, why.
Requesting a decision
On any record you can request a decision — from a specific person or from everyone allowed to decide. The answer and its reasoning are documented. This enforces nothing; it keeps the record.
Enforcing approvals
For status changes your organisation can set rules: this step needs an approval — or a four-eyes principle where the same person never both requests and approves. The database enforces this, not the UI; technical skill does not get around it. A de-minimis threshold exempts small cases.
The worklist
Open requests that concern you live here: what you can decide, what you requested yourself, what has been decided. Rejecting always requires a reason. If a record changes before it is decided, the request expires — nobody approves what they never saw.
What's inside
- Approvals
- Request
- Approve
- Reject
- Withdraw request
Fits together with
Other blocks from the same area.
Dashboard
The dashboard is your home screen: an operational overview of every area you have access to – a traffic light per area, numbers that need action, a 30-day due-date timeline and status distributions.
M02Settings
This is where your company's central settings live, used by all other modules.
M03Data import
Move your existing data into Usable effortlessly: upload a file (CSV; just save Excel as CSV), columns and the delimiter are auto-detected, duplicates flagged — then import.
M04Users
This is where you manage who has access to the app, what state each account is in (invited, active, deactivated) and which role and permissions each person gets.