---
title: "Understand whose permissions a run uses | Grafana Labs"
description: "Explain why the creator should test an automation that runs as a user."
---

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

# A test should represent the scheduled run

The checkout summary can only use resources available to the identity executing it. For an automation configured to run as **User**, the trigger determines whose access and usage apply:

```
flowchart LR
    accTitle: Execution identity for automations configured to run as User
    accDescr: A manual run uses the permissions and Assistant usage of the person who starts it. A scheduled run uses the automation creator's permissions and Assistant usage.
    subgraph U["Run as: User"]
        M["Manual run"] --> I["Person who starts it"]
        I --> MP["Their permissions
and Assistant usage"]
        S["Scheduled run"] --> C["Automation creator"]
        C --> CP["Creator's permissions
and Assistant usage"]
    end
```

## Why the creator’s test matters

A teammate’s successful manual run doesn’t prove that the creator’s scheduled run can access the same data. When the creator tests the prompt, both triggers use the same identity.

Access can change after testing. A summary that previously worked can fail if its creator loses access to a required data source.