> 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/saas-introduction-network-owner.md). # Introduction The EXADS Admin Panel provides a single interface for you to manage all aspects of your business, from the Ad Server as a whole to both Advertiser and Publisher accounts. Several features are available for those that manage Ad Servers, enabling them to administer all of the accounts that they control.

Feature	Uses
Role Based Access	Role-based access enables users to have varying levels of permissions when accessing the Admin Panel.
Quick Navigation	The Quick Navigation menu allows you to instantly see the Admin Panel as an Advertiser, Publisher or both.
Ad Server Dashboard	The Ad Server Dashboard allows you to see at a glance how your Ad Server is performing.
Ad Server Statistics	You can see comprehensive statistics reports for your Ad Server and filter it by Advertiser and Publisher.
Accounts tab	The Accounts tab allows you to add, edit and archive accounts on your Ad Server. It also allows you to log in as any user on your Ad Server.
Sites & Zones	The Sites & Zones tab allows you to manage, edit, filter and navigate to all the sites and zones available in your Ad Server and by Publisher.
Campaigns	The Campaigns tab allows you to manage, edit, filter and navigate to all the campaigns available in your Ad Server and by Advertiser.
Payments	The Payments tab allows you to manage all transactions for Advertisers and Publishers on your Ad Server.
Admin	The Admin tab allows you to configure the settings of your Ad Server. It also allows you to add, edit, and delete admin users of your Ad Server.

--- # 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/saas-introduction-network-owner.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.