Skip to content
Book a demo

Atlas documentation

All documentation
Documentation

Version 2026.11.23

On this page

Atlas3 new3 changed2 fixed

App

New

Pin artifacts to your chat home

You can now pin artifacts and data apps so they are one click away. Use the pin button on a row or card in the Artifacts list, in the full-screen viewer header, or on a card on the chat home page. Pinned artifacts appear in a Pinned row under the message box, newest first. If you have more than eight, "View all" opens the Artifacts list showing only your pins. Pins are personal and kept per workspace, and an artifact you lose access to leaves your pins until you get access back.

Below your pins, a Suggested row shows up to four artifacts that colleagues shared with the workspace or made public. Each card says why it is there: "Popular in this workspace", "Suggested for you" or "Recently shared". You can pin a suggestion straight from its card.

New

Choose which tools from an MCP server the assistant can use

Owners can now limit an external MCP server to the tools they trust. In Settings → MCP servers, open a server and choose either "All tools" or "Only selected tools", then tick the tools the assistant and automations may use. Each tool is marked read-only or write so you can tell which ones change data in the other system. When the server later adds new tools, they stay off until you select them.

Changed

SSO sign-in works from your identity provider's app tile

Starting a SAML sign-in from your identity provider, for example by clicking the Adverity tile in Okta or Microsoft Entra, used to fail with "Missing organization context in RelayState." unless an administrator had set a default RelayState in the IdP. Only sign-ins started from the Adverity login page worked.

Each organization now has its own ACS URL, /saml/acs/<organization id>/, shown in the SSO settings and the SP metadata. To enable sign-in from the app tile, update the ACS (Reply) URL in your IdP to the new value. Existing setups that use /saml/acs/ keep working as before.

Changed

The data-app builder checks the app it built

The data-app builder used to save an app without ever seeing it run, so a script error could leave every chart showing an error message. After each save, your open chat page now renders the app out of sight and tells the builder which scripts failed and which panels show an error, and the builder fixes them. Once the app shows no errors, a screenshot of it is checked against a rubric for layout, chart readability, colour and polish, and the builder makes the listed changes before it hands the app back. When no chat page is open, the build works as before.

Fixed

A stopped automation run keeps its findings and says why it stopped

When an automation run is stopped because it ran too long, or because one step made no progress for 10 minutes, the run page now says so ("Stopped: time limit reached") and shows the findings the run had already recorded, marked as partial. The notification you get names the reason and how many findings were saved. Before, the run showed "Did not complete" with no reason and an empty findings list.

Fixed

Budget plans compare against recent spend

A budget plan from a marketing mix model used to measure itself against each channel's average spend over the whole fit period. When spend had grown or shrunk over that period, the plan could call a cut an increase, and its expected uplift mixed two things: spending a different total and splitting it differently.

Plans now compare against what each channel spent in the most recent periods of the data, as many periods as the plan covers. The expected change in outcome comes in three figures: the total, the part that comes from changing the total budget, and the part that comes from the new split. The chart of expected outcomes shows recent spend, the same split at the plan's budget and the optimized split side by side. The default limits (half to double) and the level a channel is held at follow recent spend too. Plans made before this change keep their earlier figures.

Data sources

New

Choose which Google Ads accounts a data source can reach

Admins can now limit a Google Ads data source to the accounts it should use. Open the data source's Account access page, from the data source edit panel or right after connecting a new Google Ads source. It starts on Include all accounts. Untick it to browse the accounts the connection can reach as a tree: open a manager account with its chevron to see its clients, and filter by Available, Selected or All, or search by name or account ID (shown as 123-456-7890). A manager's checkbox selects or clears all of its current clients and shows how many are selected. Refresh list looks for accounts added since the last check. Save access returns you to the data sources. Accounts that are removed, that the connection cannot read, or that are cancelled, closed or suspended are shown but cannot be selected, and accounts the connection has not seen before carry a "New" badge.

Saving switches the source to selected accounts only. Agents, chat, the API and data retrieval refuse accounts outside the selection, agent changes to campaigns are held to it too, and account listings no longer show them. A request on a manager account covers only its selected clients. Selecting a manager selects the clients it has today; a client added later stays blocked until someone selects it, and tenant owners are told once about new accounts a restricted source can reach.

Narrowing the selection removes the data already landed for the accounts you remove. When saving would remove landed datasets, a confirmation says how many. The data is fetched again on demand if you select the account later.

Changed

A shorter, clearer way to add a data source

Adding a data source takes fewer decisions. Sources with a single sign-in method, such as Google Ads and PostgreSQL, skip the authentication-method step, and sources with several start with the first method selected. Google Ads no longer asks for a login customer ID: Atlas works out which manager account to use for each request.

The Configure step now holds just the name and the mode. Schedule and collection filters sit under Sync settings, collapsed until you need them, and API sources such as Google Ads don't show them at all. Atlas suggests a free name, adding the signed-in account or a number when the plain name is taken, and tells you on the spot if a name is already used.

Choosing which workspaces can use the source is now its own step, shown as the workspace tree with the workspace you were last in already selected. The review page only previews collections when your filters narrow them down.