Can our whole team folder be trusted at once?

Yes — ask your administrator to add the folder to the trusted folders. Every project beneath it then opens without the prompt, on every computer the policy reaches.

Is there a list of trusted projects I can edit?

Not yet. Trust is added by Trust this project and by saving a trusted project; the oldest entries drop off on their own.

Project trust — opening projects from someone else

Project trust — opening projects from someone elseWhy a project from another computer or person opens paused, what is paused, how to trust it, and how administrators pre-trust folders or switch the prompt off. A project file is not only data. It can carry schedules flagged to run at startup, catch-ups for slots missed while it was closed, bound queries that re-run on open, pipelines, imports, exports and e-mails — and the local database those run on can read and write any file you can. So a project that came from another computer or person must not be able to do any of that just by being opened. A project opened from a location you have never saved to or trusted on this machine — an .atx double-clicked from an e-mail, a copy on a share, a cloud copy, a browsed file — opens normally, with a strip under the ribbon: "This project came from another computer or person.

Projects from somewhere else — trust before anything runs

A project file is not only data. It can carry schedules flagged to run at startup, catch-ups for slots missed while it was closed, bound queries that re-run on open, pipelines, imports, exports and e-mails — and the local database those run on can read and write any file you can. So a project that came from another computer or person must not be able to do any of that just by being opened. A project opened from a location you have never saved to or trusted on this machine — an .atx double-clicked from an e-mail, a copy on a share, a cloud copy, a browsed file — opens normally, with a strip under the ribbon: "This project came from another computer or person. Automatic refreshes, exports and e-mails are paused until you trust it."
Until you choose Trust this project, nothing automatic runs: no startup schedules, no catch-ups, no bound-query or pinned-data reload, no file imports, no recalculation, and the background scheduler fires nothing. You can read the project, inspect its schedules and pipelines first, and anything you do by hand still works, so nothing is lost by waiting. Trusting remembers the project, by its full path, for you on this machine, and then runs the whole startup sequence.
Projects you create and save here are trusted automatically; saving an untrusted project does not trust it. Links inside a project are checked whenever they are followed, whether or not the project is trusted. Administrators can pre-trust the folders where approved reports live — UNC paths included — so projects beneath them open without the prompt, or switch the prompt off for an estate where every project comes from a controlled location: ANALYTICS_PROJECT_TRUST and ANALYTICS_TRUSTED_PROJECT_ROOTS, the [projects] section of config.ini, project-trust.policy.json, or Group Policy.
Folder matching respects folder boundaries and resolves .., so D:\BI does not cover D:\BI-old and a path cannot climb out of a trusted folder. A policy file that does not parse is ignored with a warning — it can never switch the prompt off by accident. Stated plainly: this is a pause, not a sandbox. What protects you is that the automatic work is never started; a query you run yourself on an untrusted project runs with your own rights, as it always did.

In detail

Trust a project that opened paused: Open the project → Strip under the ribbon → Trust this project

When a project opens paused

A project is paused when it is opened from a place you have never saved to or trusted on this computer. Typical cases:
an .atx file double-clicked from an e-mail attachment or the Downloads folder;
a copy on a network share, a USB stick or a synced folder opened with File → Open;
a cloud copy of a project;
a project loaded through the browser in server mode, or a shared project package — these arrive without a file location to remember, so they are asked about every time until you save them somewhere and trust them.
A project opens without asking when any of these is true:
you created it here (File → New project) and saved it on this computer;
you trusted it before, at the same location;
it lies in a folder your administrator has marked as trusted;
your administrator has switched the prompt off for your organisation.

What you see

The project opens normally, with a yellow strip under the ribbon:
Untrusted project
This project came from another computer or person. Automatic refreshes, exports and e-mails are paused until you trust it.
The status bar says the same thing, so it is visible even after the strip is hidden.

What is paused, and what still works

Schedules flagged to run at startup — Reading every sheet, dashboard and report
Catch-ups for scheduled slots missed while the project was closed — Looking at every query, pipeline, schedule and PDF report definition
Reloading bound queries and pinned data when the project opens — Running a query, a pipeline or a refresh yourself
File imports and recalculation at open — Editing, saving and exporting by hand
Everything the background scheduler would fire: refreshes, pipelines, saved queries, PDF reports, exports, e-mails and alerts — Ask Greg and every other manual action
Nothing is lost by waiting. The startup work is held, not thrown away, and runs in full the moment you trust the project. If you open a different project instead, the held work is dropped without running.

Trusting a project

1. Open the project. The Untrusted project strip appears under the ribbon.
2. Look through it before deciding: the sheets, the SQL behind pinned data, the pipelines (Transform → Pipeline → Pipelines), the schedules (File → Scheduler), and where PDF reports, exports and e-mails would go. Nothing runs while you look.
3. If you know where the project comes from and what it does, click Trust this project.
4. The held startup work runs straight away: startup schedules, catch-ups and data reloads. The background scheduler starts firing this project's schedules.
5. From now on the project opens without asking, as long as you open it from the same location.
This is a pause, not a sandbox. What protects you is that automatic work never starts on its own. A query or pipeline you run yourself on a paused project runs with your own rights, exactly as it always has — so look before you run anything from a project you do not know.

Keep paused

Keep paused hides the strip for the project you have open. It records nothing: the project stays paused, and the next time you open it you are asked again. A remembered "no" would be a decision you could not find to undo, so there is none. To trust the project later, close it and open it again, then choose Trust this project.

How trust is remembered

Per person and per computer. Trust is stored with your own profile (in server mode, in your browser). A colleague who opens the same file is asked for themselves.
By the project's full path, and only that file. Trusting one project in your Downloads folder does not trust the others next to it.
Moving, renaming or copying a project gives it a new path, so it is asked about again. A mapped drive letter and the network (UNC) path of the same file count as two different paths.
Save As keeps trust: saving a trusted project under a new name or in a new folder trusts the new location too.
Saving does not create trust: saving a paused project somewhere new keeps it paused, because where its contents came from has not changed.
Up to 500 trusted projects are remembered. Beyond that the oldest is forgotten first, and you are simply asked once more.
The list is not part of a settings export. A settings file is exactly the kind of thing that arrives from someone else, so it can never pre-trust projects.
Hyperlinks inside a project are checked every time they are followed, whether the project is trusted or not.

For administrators: trusted folders and switching the prompt off

Two decisions can be made once, centrally, for every computer. Trusted folders: list the folders where approved reports live — network shares included — and every project beneath them opens trusted without a prompt. Prompt off: for an estate where every project comes from a controlled location, the prompt can be switched off so every project is trusted. The default is to ask, with no trusted folders.
Group Policy / Intune (HKLM\SOFTWARE\Policies\ATXInstitute\AnalyticsTable, ADMX templates ship with the installer) — ProjectTrust (REG_SZ): prompt or off — TrustedProjectRoots (list)
config.ini, section [projects] — trust = prompt or off — trusted_roots = \\corp\bi | D:\Approved (separate folders with |, because ; starts a comment in an ini file)
Machine-wide file project-trust.policy.json in %ProgramData%\AnalyticsTable (Linux /etc/analyticstable, macOS /Library/Application Support/AnalyticsTable) — "mode": "prompt" or "off" — "trustedProjectRoots": [ … ]
Environment variables ANALYTICS_PROJECT_TRUST (prompt or off) and ANALYTICS_TRUSTED_PROJECT_ROOTS (trusted folders) — prompt or off — Folders separated by ; or |
{ "mode": "prompt", "trustedProjectRoots": ["\\\\corp\\bi", "D:\\Approved"] }
Group Policy, config.ini and environment variables set the same values; a mode set there wins over the policy file. Trusted folders from all places are combined, so adding one never drops another.
Folder matching ignores letter case on Windows, treats \ and / alike, respects folder boundaries (D:\BI does not cover D:\BI-old) and resolves .., so a path cannot climb out of a trusted folder.
A policy file that cannot be read is ignored with a warning. A typo can therefore never switch the prompt off — it only ever falls back to asking.
If the policy cannot be reached when a project opens, ATX AnalyticsTable asks, rather than trusting.
The application reads the policy once per session, so a change applies from the next start. No reinstall is needed.

Common questions

I trusted a project and it asks again. — It was opened from a different path (moved, renamed, copied, or opened through a mapped drive instead of the network path), by a different person or on a different computer — or more than 500 other projects were trusted since.
My schedules did not run while the project was open. — Check for the Untrusted project strip or the message in the status bar. Until the project is trusted, the scheduler fires nothing for it.
Can our whole team folder be trusted at once? — Yes — ask your administrator to add the folder to the trusted folders. Every project beneath it then opens without the prompt, on every computer the policy reaches.
Is there a list of trusted projects I can edit? — Not yet. Trust is added by Trust this project and by saving a trusted project; the oldest entries drop off on their own.

Glossary terms on this page

KPI dashboard: definition

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.