> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/audit-activity/view-recently-created-scenarios/access-scenario-information.md).

# Access scenario information

1. Go to **Administration > Scenarios**.
2. Click the filter image next to any of the following columns to search for a specific scenario:

   * **#** - Sort by unique ID number. Typically this represents the order scenarios are created on your instance.
   * **Name** - Name assigned to a scenario.
   * **Used packages** - Apps used within a scenario. Although the package is often the same as the app name, this is not always true. For example, a webhook is gateway. You can hover over an app's icon to find the package name.
   * **Status** - Inactive, Active, or Deleted.
3. Click **Details**.

Make redirects to a page similar to the user-side scenario page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.make.com/white-label-documentation/audit-activity/view-recently-created-scenarios/access-scenario-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.