Security

Security & Compliance

Security is practical when it maps directly to job operations. These controls help keep sensitive job and claims data protected without slowing field execution.

Identity and access control

Use workspace group boundaries and role limits to prevent overbroad access.

Restrict user roles by function: estimator, field lead, claims, office admin.
Require periodic review of group membership and pending invites.
Disable old integrations and rotate service credentials on a schedule.

API and integration governance

Protect API keys and external tooling channels with auditability.

Store secrets only in deployment environment variables.
Create API keys with least-privilege scope and clear ownership.
Monitor and disable keys after role changes or contractor churn.

Operational auditability

Keep claims and job actions traceable for internal and partner review.

Keep standardized task comments and status transitions intact.
Use one source of truth for closeout evidence and document packages.
Review exception handling monthly and document corrective actions.

Quarterly checkpoint list

Workspace access reviewed at least monthly
No stale service tokens older than one quarter
Sensitive documents tagged to job scopes, not individual users
No bypass workflows for high-risk changes

Related controls and plans

Bring your own OpenClaw Pricing Automation Playbook

Contractorfy roofing operations

Operations

Opening the job workflow.

Bringing up roofing CRM records, documents, tasks, and handoff controls.

Roofing workflow modules

Opening route data and controls.

Syncing

Workspace

Records

Actions