Albums and views
Draw your own pages with real applications, or open a generated view.
On this page
Design > Views holds two kinds of pictures. Generated views are drawn by Atlas from the model, for example everything within two hops of an application. Pages are canvases you arrange yourself. Both live in albums.
Three tabs
| Tab | What it holds |
|---|---|
| My | Your personal pages, grouped by album. Only you can see them. |
| Library | Pages shared with the workspace, grouped by album, followed by the built-in views such as Landscape and Capability map. Everyone can see shared pages; admins, architects and app owners can edit them. |
| System | The albums Atlas generates from the model, followed by your saved viewpoints. Open one, or copy a viewpoint into your album to draw on. |
Views opens on System. Access to personal pages and saved viewpoints depends on whether that feature is enabled in your workspace.
Open a generated view
| Album | What you can follow |
|---|---|
| Integration maps | An application's inbound and outbound integrations and recorded middleware. |
| Landscape views | Groups such as hosting, criticality, data classification or owning team. Missing values appear under Not set. |
| Data lineage | Applications and integrations linked to a particular data object. |
The diagrams show recorded relationships. Hover over a box to highlight its connections, select it to open the fact sheet, or download the page as SVG. Use Hide middleware to see the connections without separate middleware boxes.
Other views in Library
Open the full TIME view at /views/time in Atlas to compare applications by technical fit (left to right) and business fit (bottom to top). The four quadrants are Migrate (high business, low technical), Invest (high on both), Eliminate (low on both) and Tolerate (low business, high technical). Bubble colour shows the recorded TIME classification; a dashed outline means that classification differs from the quadrant implied by the scores. Use the domain and classification filters to focus the view, and choose bubble size by integration count, equal size or annual TCO when cost access is available. Applications missing either fit score appear in Not assessed instead of on the chart. Select an application to open its fact sheet, expand the chart to fullscreen or download it as SVG.
The capability map in Library shows the whole capability model on one page, in Strategic, Core and Supporting bands, with each capability numbered by its Atlas no. Choose a depth (L1, L2 or L3) and a lens: APQC match colours each capability by how well its APQC reference fits, Improvement goals highlights the capabilities a goal points at, and App support and Alignment coverage show supporting applications and strategic coverage. Search by name, Atlas no., ext id or APQC number. Select a capability to see its facts and APQC references, then choose Open in BCM to work on it under Capabilities.
Draw a page
Choose New page, give it a name and an album, and decide whether it goes in the Library. On the canvas, Add > Application opens a searchable list of the applications in the model; an application already on the page is marked On canvas. Add > Capability, Add > Data Object and Add > IT Component open the same kind of list for capabilities, data objects and IT components, so a page can explain a change across layers. Add > Note places a sticky note.
Every card is the real element, not a drawing of it. Its name comes from the model, and an application card also shows its In and Out integrations, so the page stays correct when the model changes. Each card links to its fact sheet; a data object card opens the data object. Removing a card from the page does not remove the element from Atlas. If an element is archived or deleted, its card says Removed from the model. If Atlas could not load the model when you opened the page, the page says so and the cards keep their place.
A page can also hold cards of the other element types in the model, such as processes, customer journeys, value streams, interfaces, user groups, people, providers, contracts, objectives, strategy themes, initiatives, transformations, requirements, risks and AI systems. They are not in the Add menu; they are meant to arrive with an imported Archi view once that import is available. Each one shows its live name and type, and links to its fact sheet; a strategy theme card has no link, because a theme has no fact sheet page of its own.
Drag cards to arrange them; the page saves itself. The toolbar switches between curved and step lines, lays the cards out automatically, and shows or hides the minimap.
Draw an integration
Drag from the right edge of one application card to another application card. Atlas creates an integration in the model, from the first application to the second, and shows it on every page and fact sheet where both appear. Add the protocol, data format and data on the integration's fact sheet afterwards. You need the admin, architect or app owner role; readers can look but not connect.
Copy a generated view
On the System tab, or on a generated view, choose Copy to my album. The view becomes a personal page with the same applications laid out automatically. From then on the layout is yours; the cards stay live. The same button sits on a data object's View lineage canvas, which shows the applications that create, read, update or delete the data object and the interfaces that carry it, with CRUD on every card and line.
Sharing
Pages are shared inside the workspace through the Library. Public read-only links for people outside Atlas are not open yet.
For who can see or edit a page and how to check sharing, see Share views with your team.