Company approval controls

Owners and company administrators configure these options in workspace settings and on each job:

• Workflows → Approval policies: configure independent approval, create purchasing chains, and select a company default. No separate feature switch is needed.
• Jobs → Regions: add a region or division and choose its purchasing policy. Creating an empty region saves immediately and does not change access or approvals.
• Job → Settings → Region and purchasing: open the panel to choose that job’s region and purchasing policy. Add a region from the region list. Manage policies opens Workflows and brings you back to this job. Closing the panel saves. A review appears only when a pending approval is affected.
• Jobs → Job access: leave this off unless some people should only open assigned regions and jobs. Owners and administrators always see every job. Turning it on does not hide jobs until you open a member and tick their regions and jobs. Their existing role decides what they can do. Set limited people back to all jobs before turning it off.

Open a member from Members and tick the regions and extra jobs they can open. Their role above is what they can do on those jobs. The change shows its impact before it is saved.

Existing jobs keep Existing approval settings until you explicitly choose inheritance or a published policy. Creating a policy alone does not switch existing jobs to a new route.

These controls save immediately. Existing workflow settings retain their usual Save changes button.

Purchasing approval policies

Publish a named policy with ordered steps. A step can target named people or an eligible role, and can apply to a gross value range or selected order types. Amounts use your workspace currency. Keep a catch-all step for orders that do not meet a specialist condition; otherwise the order is blocked for route repair.

Select a company default, an optional region default, or a job-specific policy. Choosing Existing approval settings stops inheritance. Publishing another version does not rewrite requests already awaiting approval.

For amendments, choose whether rules assess the individual increase, revised total, or accumulated positive increases since the last explicit approval. Reductions do not erase accumulated increases. Supplier, order-type, and coding changes are reassessed even if the total stays the same.

Independent approval

Separate controls can require independent approval for expenses, estimates, and orders. Under a strict rule, a missing approver blocks the request instead of allowing the submitter to approve it.

In Approvals, choose Review approval route to inspect the submitted revision and completed steps. An administrator can replace the current approver with an eligible person and a recorded reason. Repair cannot bypass independence or grant approval authority.

To edit a pending document, withdraw it with a reason, make changes, then use its usual submit or send action. Resubmission creates fresh evidence and uses the policy effective at that time.

Regions

A region or division is for access and purchasing rules. A development, phase, or plot is a separate structure and is not a region.

A job can belong to one region. Set that on the job, not from the Jobs list in workspace settings. Each person can have a different role in each assigned region, with a direct job role taking precedence.

Use the access preview to review jobs gained or lost and pending routes that need rechecking before applying a change. Automatically listed project-team members do not count as explicit access assignments.

Suppliers, customers and libraries remain shared under their separate permissions. Job history shown inside a directory record respects project access.

A person limited to assigned jobs sees those jobs on company screens and in the top-bar job selector. A full workspace archive still requires unrestricted access.