> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/ad-server/admin.md).

# Admin

As a Super Administrator or Administrator you can use the **Admin** tab to configure network-wide settings, governance controls, and internal access.

These settings affect your entire Ad Server. Review changes carefully before enabling integrations, modifying policy controls, or assigning administrative roles.

## Integrations and Network Controls

* [Apps](/ad-server/admin/saas-apps.md) — configure chat, security, data, and two-factor authentication integrations.
* [Accounts](/ad-server/admin/saas-admin-settings-accounts.md) — enable automatic archiving for inactive client accounts.
* [Campaigns](/ad-server/admin/saas-admin-settings-campaigns.md) — configure email tokens, creative limits, and campaign daily limits.
* [Categories](/ad-server/admin/saas-admin-settings-categories.md) — maintain the categories used across sites, zones, and campaigns.

## Governance and Access

* [Compliance](/ad-server/saas-campaigns-tab/saas-compliance.md) — review advertiser campaigns and manage Compliance users.
* [Blacklists](/ad-server/admin/saas-admin-settings-blacklists.md) — block domains from being used in publisher sites.
* [T\&Cs and Privacy](/ad-server/admin/saas-admin-settings-t-and-c-and-privacy.md) — maintain policy URLs and request client re-acceptance.
* [Users](/ad-server/admin/saas-admin-users.md) — create, manage, archive, and assign roles to internal users.

{% hint style="warning" %}
Network-wide changes can affect every client account. Confirm their impact before saving.
{% endhint %}


---

# 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://docs.exads.com/ad-server/admin.md?ask=<question>&goal=<user_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.