Your application knowledge starts here.
Register a project, then publish its first source snapshot to explore its relationships.
Loading project…
Your application, in business terms
Start with a responsibility, a rule or a process. Follow one connection at a time to see the decisions, work and information behind it.
Choose a published source version to explore its recorded connections.
Browse visible map items with the keyboard
This map describes source declarations and recorded business intent. Default roles can differ from a company’s permissions. Dashed connections are suggestions that need checking. Named inputs and outputs are process artifacts; a name alone does not bind them to database fields. A connection does not prove that a workflow ran, a check passed or a rule was approved.
What the application should do
Read the intended behaviour, important exceptions and reported checks for this exact version.
Detailed flows by business area
Choose an exact source version to see its area inventory.
Published detail is separate from business approval, executed checks and live permissions. A high-level overview does not establish detailed coverage.
Browse all business areas
Associations are declarations tied to this exact source, not inferred access grants.
Select an exact source version to explore supported calculations, decisions and destinations.
Follow the business process
Choose a declared process, follow its arrows and select a step to understand the work and recorded responsibilities.
Declared process — business review required. Role labels and RACI describe source templates; a company’s current matrix may differ. They do not prove effective tenant permissions or that a workflow ran.
Choose a source version and a declared business process.
Directed process map
Declared flowScroll the map to follow arrows. This view shows at most 400 steps and 1,000 connections. The step list below provides keyboard access to the same declared flow.
Process steps
Step meaning
Who does what
Explore the recorded roles, their process involvement and default responsibilities for this source version.
Source templates describe defaults. A company's current matrix, extra roles and individual assignments can differ. These are business roles, separate from Atlas workspace access.
Business roles
Role responsibilities
Choose a role to see its recorded responsibilities.
Test the business behaviour
Keep expected and actual results attached to the application version you tested.
Report a behaviour mismatch
Publish a source snapshot before exploring relationships or recording business requirements.
Publish a snapshot from your repository
Set ATLAS_TOKEN in your terminal. Keep the access key out of command arguments.
Find an entity
Source relationships
Evidence, not runtime proofFields, functions and endpoints connect through source evidence and declared requirements.
Preserve the business intent
Requirements describe intended behaviour for a source snapshot. Source links and test associations remain unverified until their checks are run.
Publish and select a source snapshot before recording a requirement.
Record a business requirement
Requirement trace
Select “Trace requirement” to inspect its source and test associations for the selected snapshot.
Check the reach of a change
Start with the source paths you intend to change. Atlas finds related requirements, possible dependents and declared tests.
Change context
Review a proposed change to see the requirements and source relationships that need attention.