Separate contexts
Platform operators, tenant staff, and clients work in distinct account contexts with different information and actions.
A Platform administrator and a tenant administrator do not share the same role.
Approvals and governance
Give sensitive land work a clear decision path.
Pole keeps the current record, the responsible role, and the next decision together when a change needs closer review.
New-plot approval path
An illustration of a review sequence for a proposed plot record. Actual access and review paths depend on the organization and record.
Example data · not a customer record
- 01SubmittedNew plot record includes its source CRS and geometry.
- 02CheckedThe scoped review evaluates validity, containment, and approved-plot overlap.
- 03DecisionAn authorized reviewer accepts or rejects with recorded context.
- 04Next viewThe people working from this record can see the updated review outcome.
The decision model
The screen explains the work. The system checks the authority.
A visible button is never the permission. Pole checks the current account and record before the supported action can move forward.
Appropriate actions
Pole checks whether the current account can take the supported action on the record in front of it.
Coverage is tied to the individual workflow rather than presented as one universal control.
Review queues
Supported land and operations changes can move through submission, review, approval, rejection, and correction with the relevant context beside them.
The available decision paths depend on the workflow being used.
Operational history
The workflows that need a record of change can show who acted, what changed, and what came next.
Pole does not present this as a universal, tamper-proof legal record.
The real-world states
A decision needs more than an approve button.
Good control is visible when access changes, records conflict, information is incomplete, or only part of a batch can move forward.
- Read-only access
- Pole can show when the current account may inspect a record but cannot change it.
- Conflict
- When work has changed underneath a decision, the user can return to the latest record rather than guessing what happened.
- Incomplete information
- A view can say when information is stale, incomplete, or temporarily unavailable instead of presenting certainty.
- Mixed outcomes
- Where a workflow handles a group of records, outcomes can distinguish the records that moved forward from those that need attention.
Organization access
Review one land decision path.
Start an organization access request, or prepare an email describing the roles, reviews, and exception states your team needs to assess.