Documentation

Who can see what

The four access classes, the levels each one offers, and the sentence each level grants.

Access in PadFlow is not a list of roles with a fixed set of powers. It is four classes of sensitive thing, and a level per class per person. A superintendent can hold edit on the schedule and none on money. A lender can hold view on money and nothing else.

Two consequences are worth knowing before you read the table.

Money has a level the other three do not. view_redacted shows the rows without the amounts: a budget line still lists its cost code, its stage and whether it is committed, and the figures read as dashes. It exists so somebody can track progress without being shown price.

A level is enforced by the database, not by the menu. Hiding a tab is a courtesy. Typing the address of a page you do not hold the level for gets you the same refusal.

Schedule & dates

Covers tasks, critical dates, permits and deadlines.

none
No access to this class at all.
view
Can see the schedule.
edit
Can move dates and tasks.
approve
Can approve schedule changes.

Money

Covers budgets, draws, invoices, pay applications and change orders.

none
No access to this class at all.
view_redacted
Can track budget status without seeing amounts.
view
Can see all financials.
edit
Can edit budgets and build draws.
approve
Can approve draws.

Documents

Covers the document register, filing and obligations.

none
No access to this class at all.
view
Can read documents.
edit
Can upload and file documents.
approve
Can approve documents into force.

Settings & people

Covers workspace settings, integrations and who else gets in.

none
No access to this class at all.
view
Can see workspace settings.
edit
Can change settings and invite people.

Known limits

A level applies across the workspace, or across the projects a membership names. There is no per-page override, and there is no level between view and edit.