Contractors Route Reference
Understand contractor access grants, native external job packs, portal access, staged submissions, and the admin review queue.
Before you start
- You need route-level detail for external contractor job-pack review.
Expected outcome
You can distinguish contractor profile and grant APIs from the Contractors review route and understand how staged submissions merge.
What this route is for
Contractors is the office-side review queue for staged contractor submissions. It lets admins filter submissions, inspect evidence and proposed status changes, and approve, request changes, or reject before official work-order records are updated.
Contractor profiles and grants are backed by admin APIs. The visible route is currently focused on submission review rather than full contractor directory management.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | contractors |
| Visibility | Customer-facing admin route for admin users. |
| Capability notes | Requires work-order capability. |
| Direct inbound | Shell navigation and contractor submission workflows. |
Main regions, dialogs, and controls
| Surface | What it does |
|---|---|
| Submission queue | Filters contractor submissions by status. |
| Review panel | Shows contractor identity, work order, proposed status, summary, media count, work-item count, checklist count, and review note. |
| Approve and merge | Accepts a submitted update and merges allowed changes into the official work order. |
| Request changes | Rejects the current submission with a request for correction. |
| Reject | Rejects the submission without merging. |
Key actions
- Filter submissions by
submitted,accepted,rejected,draft, orall. - Select a submission for review.
- Add a review note.
- Approve and merge staged work.
- Request changes.
- Reject staged work.
Contractor access model
| Record | Purpose |
|---|---|
| Contractor | Organization-scoped external delivery identity. |
| Contractor access grant | Expiring, revocable work-order access for email, native app user, or both. |
| Contractor access event | Audit trail for grant creation, sending, viewing, expiry, revocation, denial, native binding, and submission. |
| Contractor submission | Staged contractor update awaiting admin review. |
Grant permissions are view, view_download, and submit_evidence.
Native and portal access
Native external job packs are bound by recipientUserId. This allows an existing Deucalion app user outside the sending organization to receive a pack without being added to the organization.
Portal access is token-based. Portal and native job-pack responses use no-store and noindex headers.
Outputs and side effects
- Approving a submission can update work-order status, work items, checklist responses, and evidence references through the controlled merge path.
- Rejection and request-changes decisions update submission status and review metadata only.
- Contractor grants and submissions remain organization-scoped.
Inbound links
- Shell
Contractorsnavigation. - Native or portal contractor submissions after a grant with
submit_evidence.
Outbound links
- Work-order context through submission rows.
- Admin review decisions update or preserve the official
Work Ordersstate.
Indirect handoffs
- Work-order quality controls what the contractor sees.
- Contractor evidence does not become official until an admin approves and merges it.
- Native app delivery depends on app user identity, not organization membership.
Troubleshooting
| Symptom | What to check |
|---|---|
| A submission is not reviewable | Only submitted submissions can be approved, rejected, or returned for changes. |
| A contractor cannot submit | The grant must have submit_evidence permission. |
| A native user cannot see a pack | Check recipientUserId, expiry, revocation, and contractor active state. |
| A merge did not change the work order | Check the review result and whether the submission had mergeable payload fields. |
Work Orders Route Reference
Understand the remedial work queue, assignment and scheduling actions, and the way work-order state feeds mobile execution and finance.
Organization Route Reference
Understand workspace profile, invitations, seat and billing flows, service policies, and feature-access controls.