Overview
Use this article when you need to apply dashboard layout presets in Atlas Verified. It explains where to start, what information to check, and what should happen after the action is complete.
This work usually involves workspace columns, menu items, quick actions, and open panels. Keeping that context clear helps prevent mistakes, especially when you belong to more than one organization or when similar suppliers, shipments, or documents have similar names.
Before you begin
You need an active Atlas Verified account and access to the correct organization.
Keep the related workspace columns or menu items nearby if this workflow depends on existing records.
How to do it
Sign in to Atlas Verified and confirm you are in the correct organization.
Open the dashboard after signing in.
Use the dashboard and navigation control on the screen, then review the fields and status messages before saving.
Review the required fields, linked records, recipients, files, or status details before submitting.
Save or submit the action, then confirm the status message, updated row, generated file, or detail view.
What happens next
After the action completes, Atlas updates the related workspace so the result can be reviewed by your team. Depending on the workflow, you may see a new record, an updated status, a sent request, an uploaded document, a generated report, or a refreshed detail view.
Tips
Use the most specific name, reference, recipient, or date available so teammates can identify the result later.
Review linked records before submitting if the workflow affects a supplier, shipment, document, signature, or verification request.
If the action creates something new, open the result immediately and confirm it contains the expected details.
Troubleshooting
I cannot find the action.
Your role or plan may not include it, or you may be looking in the wrong organization. Switch to the correct organization and ask an admin to confirm access.
The result looks wrong.
Open the detail view and correct the editable fields before relying on the record or sharing it externally.
The action failed.
Refresh once, try again, and contact support with the affected record name, approximate time, and the message shown on screen.