Summary
Required documents by verification type explains how this part of Atlas Verified works, where it appears in the product, and why a user would open it during daily compliance or trade operations. Use it to understand the purpose of verification flows (/verify/[token] for recipients), the records it connects to, and the next workflow a user is likely to need.
Before you begin
Sign in at app.atlasverified.ai.
Steps
Sign in and open verification flows (
/verify/[token]for recipients).Locate the main module for Required documents by verification type using the sidebar or Intelligence menu.
Scan tabs and sub-panels named in this article; open one record to see typical fields and actions.
Use Get Help (Atlas Agent) if a control is missing from your plan (GS-010).
Expected result
You know where Required documents by verification type lives in the app, what the feature does, and which tabs or related records matter for your role.
Tips
Keep the related shipment, supplier, document, or organization open while you work.
Common issues
Wrong organization — Switch in the header (AT-008).
Persistent errors — See Troubleshooting (TS-012) or category TS articles.
Related articles
VF-001
VF-002
VF-003