Resources / Security
Clear access. Visible actions. Better questions.
Use this guide to prepare your account review, discuss data requirements and understand the controls around operational actions.
This page is a review guide. For contractual commitments, certifications, retention periods or recovery targets, request the current documentation from the Prevayl team.
Account access and responsibilities
ILLUSTRATIVE RECORD
Access review worksheet
| Responsibility | Person | Review |
|---|
| Organization admin | Account owner | Authentication |
| Daily dispatch | Operations | Assignment scope |
| Payment approval | Finance lead | Action limits |
Define who needs access, then confirm the actual permissions.
- →List the people who need access and the workspaces required for their jobs.
- →Review administrator access, organization membership and authentication settings.
- →Use individual accounts so activity can be associated with the person performing it.
- →Review access when a person changes roles or leaves the organization.
- →Confirm which roles may approve sensitive operational and financial actions.
Data, integrations and retention
ILLUSTRATIVE RECORD
Know where the record goes.
ORDER RECORDVehicle · Lane · CustomerIdentify the fields required by each connection.
- Marketplace
- Listing and carrier context
- Accounting
- Invoice and payment mapping
- Customer portal
- Authorized shipment visibility
- Retention review
- Discuss export and deletion needs
- →Identify the customer, vehicle, driver and financial data needed for each workflow.
- →List the external systems that receive or supply information.
- →Confirm the credential owner, permitted scope and process for revoking a connection.
- →Discuss export, deletion, retention and backup requirements with the team.
- →Request the documentation needed for your organization’s vendor assessment.
Automation and handoff controls
ILLUSTRATIVE RECORD
Prepared is different from executed.
PROPOSALRelease requestDriver identity and pickup context attached.
Approval boundaryRECORDED RESULTAuthorization decisionReviewer, decision and supporting checks.
- →Distinguish a suggestion, a prepared draft and an executed action.
- →Review the configured stage policy before enabling posting, booking or communication.
- →Keep pickup authorization tied to the relevant driver request and shipment context.
- →Confirm where the action result and exceptions can be inspected.
- →Name an operator responsible for unresolved or ambiguous outcomes.
Report a concern
Give the team enough context to investigate.
Include
- The affected page or workflow.
- When it happened, including time zone.
- What you expected and what occurred.
- Steps to reproduce and a redacted screenshot, if useful.
- A record reference and safe contact method.
Leave out
- Passwords, authentication codes and API keys.
- Full bank or payment credentials.
- Unnecessary customer or driver information.
- Unredacted exports containing unrelated records.
Use the support contact flow for the initial report. Describe the issue first and arrange an appropriate way to share sensitive evidence with the team.
Contact the team →