> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/utilities/authorization-centre/authorization-centre-fields.md).

# Authorization Centre Fields

The Authorization Centre is designed to keep track of all the user overrides that have been performed. It allows users to easily trace and investigate any authorizations that have taken place in the system.

{% hint style="info" %}
To access the Authorization Centre, go to ***Menu > Utilities > Authorization Centre***
{% endhint %}

### Authorization Centre Fields

<table><thead><tr><th width="195">Field</th><th>Description</th></tr></thead><tbody><tr><td>Code</td><td>This is a unique identifier that depicts the authorization type, such as NRI for Non Returnable Item Override. It helps in quickly referencing and locating specific overrides within the system.</td></tr><tr><td>Authorization Name</td><td>This field shows the type of the authorization that was performed, such as a pricing rule change or shipment adjustment.</td></tr><tr><td>Ref Type</td><td>This field indicates the category or type of transaction associated with the override, such as sales order, invoice, credit memo, etc.</td></tr><tr><td>Ref Number</td><td>This field shows the reference number of the transaction on which authorization has been performed, such as the sales order number.</td></tr><tr><td>Line Ref Number</td><td>For transactions that include multiple items or lines, this field specifies the line item number within the transaction that was overridden.</td></tr><tr><td>Override Value</td><td>This field shows the value that was overridden.</td></tr><tr><td>Override User</td><td>This field displays the username of the person who performed the override. It helps in tracking user activity and accountability.</td></tr><tr><td>Notes</td><td>Any additional information or context regarding the override is recorded in this field.</td></tr><tr><td>Create Datetime</td><td>This timestamp indicates the exact date and time when the override was created.</td></tr><tr><td>Created By</td><td>This field shows the username of the person who initially created the override entry in the system.</td></tr></tbody></table>

### Authorization Centre Filter

In the Authorization Centre, there is an option to filter the transaction by type. You can select the transaction type from the dropdown search filter to view the transactions with specific authorizations.

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

The types include:

* PR: Price Restriction Overide
* NRI: Non Returnable Item Overide
* ER: Edit Released Override
* SR: Sales Rep Overide
* VR: Void Released
* CR: Cancel Released
* RF: Change Re-Stocking Fee
* CIA: Cash In Advance Overide
* AP: Accounting Period Unlock
* DC: Override Defaulter Customer
* ESO:&#x20;


---

# 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://docs.xorosoft.com/xoroerp-1/utilities/authorization-centre/authorization-centre-fields.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.