> 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/the-navigation-bar/saas-network-user-profile-page.md).

# The Profile Page

As a Network Admin User in Admin View, use the **Profile** page to manage your account details and API tokens. To access it, click your username in the top-right corner.

As any Network Admin User in Admin View, you can manage and view the details of your account on your **Profile** page. To access your **Profile** page, click on your username in the top right of the screen.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FSCFVXlXGDoGfhP1tTkv8%2Fimage.png?alt=media&amp;token=7d21d0b3-01c0-429e-8c06-b873dcf5fdd9" alt=""><figcaption></figcaption></figure>

As any Network Admin User in Admin View, you can manage and view the details of your account on your **Profile** page. To access your **Profile** page, click on your username in the top right of the screen.

## Profile <a href="#profile" id="profile"></a>

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FyjlywvW7auTQdodcOpvX%2Fimage.png?alt=media&amp;token=3d2b4808-af0e-4f34-b53c-9331a55b4877" alt=""><figcaption></figcaption></figure>

At the top of this tab, you will see your username and role in bold.

### Account Details <a href="#account-details" id="account-details"></a>

In this section, you will see the following fields:

* **Username** \*
* **First Name**
* **Last Name**
* **Email**

\*not editable

## API Tokens <a href="#api-tokens" id="api-tokens"></a>

This section lists the API tokens you use to connect to the Network API. Use the **Active / Archived** toggle to switch between your current tokens and the ones you’ve archived.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FXge4fqoUcOh2Vk1Q9f3Y%2Fapi_tokens_updated.png?alt=media&amp;token=1e237da4-06e0-4547-aaf8-7a5981ff9dd2" alt=""><figcaption></figcaption></figure>

The **API Tokens** table displays all the API tokens you have created. The table consists of

| Column      | Description                                                                                                                |
| ----------- | -------------------------------------------------------------------------------------------------------------------------- |
| Name        | The token’s name.                                                                                                          |
| Status      | Whether the token is enabled or disabled.                                                                                  |
| State       | Whether the token can be used right now (see below).                                                                       |
| Created     | The date and time the token was created (YYYY-MM-DD HH:MM:SS).                                                             |
| Last Used   | The last time the token was used to log in, or a session opened with it was renewed. Shows “-” if it hasn’t been used yet. |
| Expiry Date | The date and time the token expires.                                                                                       |
| Token       | The last 4 characters of the token, masked (for example, ••••a1b2).                                                        |

State shows one of:&#x20;

| State         | Meaning                                                                 |
| ------------- | ----------------------------------------------------------------------- |
| Active        | The token is enabled and expires in more than 30 days.                  |
| Expiring Soon | The token is enabled and expires in 30 days or fewer.                   |
| Inactive      | The token is disabled.                                                  |
| Expired       | The token’s expiry date has passed, whether it was enabled or disabled. |

### **Creating a token:**&#x20;

Click **New API Token**, enter a name, set the status and click **Save**. The full token is shown with a **Copy** button and the message “Copy this token now. You won’t be able to see it again.” Copy it and store it somewhere safe, then click **Done**. The full token can’t be viewed again.

**If you lose a token:** it can’t be recovered. Create a new token, then delete the old one.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FnTlFvw49AY1v4yfLNNiG%2FAPITokenCopyModal.png?alt=media&amp;token=744dcbbc-d48f-4572-adb9-730f7fbad1cd" alt=""><figcaption></figcaption></figure>

Use these tokens to integrate with the [API](https://docs.exads.com/api/).

{% hint style="warning" %}
**Treat API tokens like passwords.** Don't share them or put them in public code. If you no longer use a token, or think it has been exposed, deactivate it and create a new one.
{% endhint %}

### Token Expiry <a href="#notifications-tab" id="notifications-tab"></a>

* Every token expires 1 year after it is created. The expiry date cannot be extended. To keep API access, create a new token before it expires.
* You get a reminder email 30 days and 7 days before a token expires, and another on the expiry date. These are security emails, so they are sent even if you’ve turned off email notifications.
* An expired token can’t be re-enabled. It stays in the list until you archive it.

### Disabling a Token

Click the edit icon and set the Status to Disabled. The token stops working immediately, and any API session using it ends. You can enable it again later, unless it has expired.

#### Disabling all Tokens

To disable all your API tokens at once:

1. Click **DISABLE ALL**.
2. In the **Disable all API Tokens** dialog, click **DISABLE ALL**.

All your tokens stop working immediately, and every integration using them stops too. Their State shows **Inactive**. You can enable each token again individually, unless it has expired.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2F9i250LqaM3cAnPzu7Vmr%2Fimage.png?alt=media&amp;token=a7e591cc-36f9-4f86-9049-ecb51792307f" alt=""><figcaption></figcaption></figure>

### Archiving a token

To archive a token:

1. Click the archive icon next to the token.
2. In the **Archive API Token** dialog, click **ARCHIVE**.

Archiving is permanent. The token stops working immediately, any API session using it ends, and it can’t be restored, edited or enabled again. Archived tokens don’t count towards the limit of 10 tokens.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FEUUTbRzbWEbXI4DllH7G%2FAPITokenArchive.png?alt=media&amp;token=be7152f3-317a-488e-a2aa-0526a78302bd" alt=""><figcaption></figcaption></figure>

#### Archived Tokens

Click **Archived** on the Active / Archived toggle to see the tokens you’ve archived. The list is read-only and shows:

| Column     | Description                                 |
| ---------- | ------------------------------------------- |
| Name       | The token’s name.                           |
| Token      | The last 4 characters of the token, masked. |
| Created    | The date and time the token was created.    |
| Archived   | The date and time the token was archived.   |
| Revoked By | Who archived the token.                     |

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FEtmmdtM58DQVyr0yLkpO%2Fimage.png?alt=media&amp;token=7578112e-f477-4fdc-b708-190f87440382" alt=""><figcaption></figcaption></figure>

**If you lose a token:** it can’t be recovered. Create a new token, then archive the old one.


---

# 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/the-navigation-bar/saas-network-user-profile-page.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.
