# Admin Actions

## Admin Actions

<figure><img src="/files/VueCQURTQpa54sldxlhU" alt=""><figcaption></figcaption></figure>

An advantage of this feature is that you (or a TMM tech) can troubleshoot problems by seeing what settings were changed, as well as when they were changed by an admin.

You can search for specific admin actions by using the "Admin Action Search" box at the top of the page. Available search parameters include:&#x20;

* **Affiliate Info**: Search by Affiliate ID and Affiliate Username.
* **Action Info**: Search by Admin Page, or conduct a Full Search.

The breakdown of admin actions lists a variety of details, including:

* **Date** - The date an admin action took place.
* **Page** - What page the admin action took place on.
* **Action** - The action that the admin took (ex. customize\_edit, edit\_cascade, etc.)
* **View** - The specific sections of a page that the admin viewed.
* **IP** - The admin's login IP.
* **Data** - On mouse-over, shows a text bubble of information from *$\_GET*, *$\_POST*, and *$\_SERVER*.

{% hint style="warning" %}
**Please Note:** As of NATS5, the Admin Actions area will be populated with every individual API request originating from the NATS5 admin interface, which will greatly clutter/inflate your logs. If you would like to only record changes in the NATS5 admin interface, then you can enable the DISABLE\_NATS5\_ADMIN\_VIEW\_LOGGING setting in the Config Admin -> Logging section.&#x20;
{% endhint %}

## Related Articles

{% content-ref url="/pages/8VHJBcYLCqZnEJT0UfQY" %}
[Affiliate Management](/nats-admin/affiliates/affiliate-management.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.toomuchmedia.com/nats-admin/support-and-maintenance/admin-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.