A dashboard is easier to share than a long report, but a link can reveal more than its title suggests. Before sending it, inspect the entire view as the recipient would, including filters and cached or example data.
Decide what the recipient needs
Remove customer names, internal links and private numbers that do not belong in the shared view. If a widget uses live data, understand which source updates it and whether the displayed information can change after you share it. Test with fictional data first.
The APX board guide says artifacts are private by default and that anyone with an enabled share link can view the shared artifact. A link needs a reachable host; making one does not itself expose a loopback-only core. The guide also warns that enabling a public address can make already-shared pages reachable, so review existing shares first.
Verify access and remove it later
- Inspect the whole page and ask a trusted tester what they can see.
- Enable only the intended share and send it to the intended audience.
- Recheck the visible data after changes or refreshes.
- Stop sharing when the link is no longer needed.
Do not expose the full control panel just to publish one view. Exporting a template without its saved memory is a separate choice from sharing a live view.
Sources
More articles
How to let an AI agent work on a site without sharing your password
A practical guide to browser handoffs, sessions and safer sign-in for AI agents.
Can an AI agent work from WhatsApp or Telegram? What to check first
Plan a chat-based agent workflow around identity, approval, delivery and privacy before connecting a messaging app.
Why an AI agent cannot use a connected tool: an MCP checklist
Troubleshoot an MCP connection in stages: scope, approval, sign-in, tool discovery and a safe test.