Summary
Use Sign a document as a recipient (/sign/[token]) when you need to complete this workflow in Atlas Verified and understand what the app changes afterward. The feature starts from /sign/[token], then usually updates a record, sends a request, creates a file, or opens a detail panel that becomes the source of truth for the next step.
Before you begin
Sign in at app.atlasverified.ai.
Signing uses the email link (
/sign/[token]); an Atlas account is not required.
Steps
Open
/sign/[token]from the signature email.Review documents to sign and field placements.
Complete required fields and apply your signature.
Click Finish or Submit — status updates for the sender (SG-005).
Expected result
The app shows the expected record, email, file, status badge, or detail panel for Sign a document as a recipient (/sign/[token]), and you know where to continue the workflow.
Tips
Dashboard quick actions (DN-004) mirror most create flows.
Use the same navigation path each time: /sign/[token].
Common issues
Wrong organization — Switch in the header (AT-008).
Persistent errors — See Troubleshooting (TS-012) or category TS articles.
Related articles
SG-001
SG-002
SG-003