> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mainwp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Difference between Client-level and Site-level Custom Tokens

> This article clarifies how custom tokens function in MainWP at both the site level and the client level. Site-level values override matching client-level values when a site value is present and are best for site-specific details.

## What You'll Learn

* Understanding site-level vs client-level token priority
* When to use each token type
* Managing tokens that share the same name
* Where to store reusable client details

***

<Info>
  **Extension Add-on** - This add-on provides standalone functionality within MainWP Dashboard. No third-party plugins required.
</Info>

This article explains how MainWP Dashboard resolves Pro Reports values when the same token exists at both the site level and the client level.

## Site-Level Tokens:

* **Stored on the site Edit screen:** Site-level values are entered in the **Pro Reports Tokens** section when you edit a site in **Sites > Manage Sites**.
* **Used first when filled in:** If a site-level value exists for a token, Pro Reports uses it before checking the client-level value.
* **Usage:** Site-level tokens are ideal for specific, unique information relevant to an individual site.

## Client-Level Tokens:

* **Fallback Mechanism:** If a token is not set or is left empty at the site level, the client-level value is used instead.
* **Stored in the Clients feature:** Client-level values come from the **Clients** area in MainWP Dashboard, including built-in client details and any custom **Client Fields** you create.
* **General Information:** Client-level tokens are suitable for information that applies across multiple sites assigned to the same client.
* **Separate data source:** Even when a token name matches a site-level token, the client-level value is stored separately from the site-level Pro Reports value.

## Managing Redundant Tokens

* **No Need for Deletion:** It is not necessary to delete tokens even if they share names between client and site levels.
* **Selective Input:** Enter values where most appropriate (client or site level) and leave the other level empty if not needed.
* **Pro Reports Prioritization:** If both levels use the same token name, Pro Reports uses the site-level value when it is filled in and falls back to the client-level value when the site-level field is empty.

## Where to Store Extra Client Details

* **Use Client Fields for reusable data:** Create custom client fields under **Clients > Client Fields**, then fill them in when adding or editing a client.
* **Use site tokens for per-site overrides:** Use the **Pro Reports Tokens** section on the site Edit screen only when a value needs to differ for one specific site.

***

## Related Resources

* [Pro Reports Extension](/add-ons/agency/pro-reports-extension-overview) - Main Pro Reports documentation
* [Available Pro Reports Tokens](/add-ons/agency/available-pro-reports-tokens) - Complete token reference
* [Create Custom Report Templates](/add-ons/agency/create-custom-report-templates) - Build custom PHP templates