> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/action-management/view-outside-of-terms-actions-as-a-partner.md).
# View Outside of Terms Actions as a Partner
Any actions that do not meet the requirements of the contract you made with your partnered brand are considered outside of terms. Unless these are manually approved by your partnered brand before the action locking date, you will not receive a payout for these actions.
{% hint style="info" %}
**Example:** If a brand has set a cap on the number of actions you can be credited for in a month, any credited actions exceeding that cap would be considered as *Outside of Terms* actions.
{% endhint %}
## View outside of terms actions
Outside of terms actions are a specific type of reversed action. To see these actions:
1. From the top navigation bar, select your **Earnings Account →** [**Pending Actions**](https://app.impact.com/secure/mediapartner/actionworkflows/mp-pending-actions-flow.ihtml).
2. From the tabs at the top of the screen, select **Outside of Terms**.
3. To view a specific brand's outside of terms actions, under *Outside of Terms Actions*, select them from the **Brand: None** drop-down menu and select  **\[Search]**.
4. To search for a particular outside of terms action by its action ID, enter that into the **Action Id search bar** and select  **\[Search]**.
5. To view more details of the action, to the left of the action date, select  **\[Add]**. More details will appear below the action.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/action-management/view-outside-of-terms-actions-as-a-partner.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
