---
title: "Separate configuration access from results | Grafana Labs"
description: "Distinguish who can see an automation from who can read its output."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Who needs the checkout summary?

The saved automation and the conversation produced by a run have different access rules. **Visibility** controls access to the saved configuration.

Personal automations appear as **Just me** to their creator. Assistant administrators with the appropriate permissions can also view and edit that configuration. **Everybody** makes the configuration available to other users with the right access.

For user-mode runs, sharing the configuration doesn’t automatically share the resulting conversation. The user who triggered the run must explicitly share the chat for others to read it.

Personal visibility is a useful starting point while the checkout prompt is being tested. A team may later need the configuration, the results, or both.