Trust and product boundaries
Understand how Pole keeps sensitive work in its lane.
Review the account separation, action checks, and operating history that support the product today—then bring the questions your organization needs answered.
What the product does
Trust starts with the right context and the right person.
Pole separates account contexts, checks actions on the server, and keeps operational history with the workflow that owns it.
- Account contexts
- Platform administration, organization workspaces, and the client portal remain distinct product and security contexts.
- Organization scope
- Pole establishes the organization context from the signed-in account before it reads or changes a supported record.
- Appropriate actions
- The server checks whether the current account can take the supported action; hiding or showing a control is never the permission.
- Sensitive requests
- Established paths use measures such as request checks, rate limits, private response handling, and selected step-up confirmation.
- Decision records
- The workflows that need an accountable change record apply the checks appropriate to that action.
- Follow-up work
- Views can refresh after an accepted change so teams return to the latest available record.
Scope
Ask the right question of the right evidence.
Product controls are useful evidence. They are not a substitute for the legal, operational, deployment, and third-party review your organization may also need.
- Certification
- Pole does not publish ISO, SOC, privacy-law, or other certification or legal-compliance claims here.
- Land authority
- Pole records operational data. It does not adjudicate ownership, verify title, certify a boundary, or replace a surveyor or registry.
- Operational assurance
- Availability, backup restoration, retention, incident response, dashboards, and alert delivery need their own current operational evidence.
- History
- Pole does not present its operational history as a universal, legally admissible, or tamper-proof audit trail.
- External services
- Email, alerts, billing, map imagery, and other third-party services have their own availability and data-handling boundaries.
Bring these questions to an evaluation
- Which Pole account context will each team use?
- Which decisions need review or a stronger confirmation step?
- Which spatial sources and coordinate details will your team bring into the record?
- Which hosting, backup, monitoring, retention, legal, and third-party-service assurances need separate review?
Organization access
Bring your review questions.
Start an organization access request, or prepare an email with the controls and assurance boundaries your team needs to evaluate.