Permission-aware quick actions
Start the construction records you are allowed to create from one grouped page while keeping the currently selected project in context.
Permission-aware quick actions: how it works in Home Builder Software
Quick actions is a page of its own, reachable from the navigation, that lays out everything the signed-in person is allowed to start. A new colleague no longer has to find the right module first and hunt for a plus button hidden in its corner. A project, a schedule activity, a work task, a shift, a daily report, a defect, a document upload, a service request, a lead, an estimate, a customer, an invoice or a finance entry all begin here.
This page, the phone bottom bar and the New button on the desktop read from one list, so the three can never offer different things. Every entry carries the read permission of its module and the write permission its save route needs, which means nothing on offer can answer with a refusal after the tap. The groups follow the order of the sidebar, and a running time entry appears as a banner with its project and a clock-out button.
When a project is active, its number and name stay in the page header and travel into the create form: daily reports, defects, document uploads, service requests, estimates, invoices and work tasks open with the job already filled in. A clear button drops that context when the next record belongs somewhere else. Nobody corrects the assignment afterwards, and no defect lands on the neighboring site because the previous project was still selected.
Permission-aware quick actions in the daily routine
A foreman finishing a walk on site taps the orange button, sees the four or five things his role may create, and starts the defect for the project he is already standing in. In the office the same page answers a different question, because a new user opens it to learn what the account can actually do. Nothing is maintained here by hand: the list changes as soon as a role gains or loses a permission, and the page follows on the next visit.
Read the documentationPermission-aware quick actions: what it covers
See available create actions grouped like the main navigation
Carry the active project into the next workflow
Show only actions permitted for the signed-in role
Permission-aware quick actions: questions and answers
What appears under Quick actions?
The page lists the create actions the signed-in user may start, grouped by the same areas as the navigation.
Does opening an action lose the selected project?
No. When a project is active, supported actions carry that project into the new record.
Use Permission-aware quick actions on your own projects
A demo runs on a project that resembles yours, with the roles and permissions your team actually uses.