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

# Designing your tenant for CMP

### Understanding Tenants <a href="#understanding-accounts" id="understanding-accounts"></a>

Tenants in the Credential Management Platform serve as distinct, logical units for managing card services and credentials. Think of them as containers that isolate and organize your card-related activities. In the past, the term 'Tenant' has been used interchangeably with 'Account.'

#### Purpose <a href="#purpose" id="purpose"></a>

Tenants enable you to segment and manage different sets of cards and services. They also allow for separate enrollments with third parties such as VISA, Mastercard, American Express, and Discover in the situation that the third party requires separate enrollments into services per-merchant.

For merchant aggregators such as Payment Service Providers (PSPs), PayFacs, and Marketplaces, this allows for clear separation of merchant data, where each merchant can have its own dedicated tenant.

#### Key Characteristics <a href="#key-characteristics" id="key-characteristics"></a>

* Each tenant is uniquely identified by a Tenant ID (an identifier always beginning with prefix *tnt*).
* Cards created within a tenant are exclusive to that tenant.
* Service configurations and settings are applied at the tenant level.

### Tenant Configuration Options <a href="#account-configuration-options" id="account-configuration-options"></a>

The platform offers flexible service configuration options at both the tenant and network levels:

#### Tenant-Level Service Control <a href="#account-level-service-control" id="account-level-service-control"></a>

* You have the ability to enable or disable services for the entire tenant.
* This provides a global setting for all cards related to the tenant.

| Service                                                                                              | Overall Service Configuration                                                     |
| ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| [Account Updater](/cmp/products-and-services/account-updater.md)                                     | Enabled/Disabled                                                                  |
| [Network Tokens](/cmp/products-and-services/network-tokens.md)                                       | Enabled/Disabled                                                                  |
| [Card Art](/cmp/products-and-services/card-art.md)                                                   | Enabled/Disabled                                                                  |
| [Duplicate Card Check](/cmp/payment-credentials/cards.md#duplicate-card-detection)                   | Enabled/Disabled                                                                  |
| [Card Attributes (Enriched Attributes)](/cmp/products-and-services/card-attributes.md)               | Disabled by default. For upgrade, please contact support via **<support@vgs.io>** |
| [3DS](https://docs.verygoodsecurity.com/cmp/products-and-services/3ds)                               | Enabled/Disabled                                                                  |
| [Account Validation](https://docs.verygoodsecurity.com/cmp/products-and-services/account-validation) | Enabled/Disabled                                                                  |

#### Network-Level Service Control <a href="#network-level-service-control" id="network-level-service-control"></a>

You can further refine service settings by enabling or disabling services at the network level (e.g., Visa, Mastercard). This allows for granular control over service availability based on the card network. Both **Account Updater** and **Network Token** services can be individually enabled or disabled per network, based on your business requirements.

| Service                                                          | Network-Level Configuration |
| ---------------------------------------------------------------- | --------------------------- |
| [Account Updater](/cmp/products-and-services/account-updater.md) | Enabled/Disabled            |
| [Network Tokens](/cmp/products-and-services/network-tokens.md)   | Enabled/Disabled            |

#### Enrollment Types <a href="#enrollment-types" id="enrollment-types"></a>

The platform supports two enrollment types, determining how services are activated:

#### **On-Create Enrollment**

* This is the default setting.
* When a card object is created, the system automatically processes and activates the services enabled for the tenant.
* A webhook notification is sent upon successful service activation.

#### **Manual Enrollment**

* With manual enrollment, card creation does *not* automatically trigger service activation.
* You must explicitly invoke individual service endpoints to perform actions like network tokenization or account updater participation.
* This provides greater control over the timing of service activation.

| Service                                                          | Enrollment Type                 |
| ---------------------------------------------------------------- | ------------------------------- |
| [Account Updater](/cmp/products-and-services/account-updater.md) | On Create Card (Default)/Manual |
| [Network Tokens](/cmp/products-and-services/network-tokens.md)   | On Create Card (Default)/Manual |


---

# 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.verygoodsecurity.com/cmp/platform/cmp-account.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.