> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-configure-data-storage-optimizer/pdso-hcp-configuration/hcp-tenant-configuration.md).

# Configure a tenant in Content Platform

To create a Content Platform tenant, you need the administrator role.

You must create a Hitachi Content Platform tenant for Data Optimizer. In most cases, Data Optimizer instances create their own buckets, so you need to properly configure namespace defaults to result in properly configured buckets.

Use the following steps to configure a tenant in Content Platform.

1. In the top-level menu of the Hitachi Content Platform System Management Console, click **Tenants**.

   The Tenants page opens.
2. On the Tenants page, click **Create Tenant**.

   The Create Tenant panel opens.
3. On the Create Tenant panel, create a tenant, making sure to:
   * Allocate enough quota for all anticipated Data Optimizer instances.
   * Enable versioning.\
     See the **Hitachi Content Platform** product documentation for more information.
4. Use the following steps to enable the management API (MAPI), so that Data Optimizer instances can create buckets.
   1. Log into the System Management Console or Tenant Management Console using a user account with the security role.
   2. In the top-level menu of either console, select **Security** > **MAPI**.

      The Management API page opens.
   3. In the **Management API Setting** section on the Management API page, select **Enable the HCP management API**.
   4. Click **Update Settings**
5. Enable MAPI at the cluster level.
6. Use the following steps to configure namespace defaults for the tenant:
   1. From the Content Platform Tenant Management Console, select **Configuration** > **Namespace Defaults**.
   2. In the **Hard Quota** field, type a new number of gigabytes or terabytes of storage to allocate for an individual Data Optimizer instance namespace and select either GB or TB to indicate the measurement unit. The default is 50 GB. The maximum value you can specify is equal to the hard quota for the tenant.
   3. Set **Cloud Optimized** to **On**.
   4. Set **Versioning** to **On**.
   5. Enable version pruning older than 0 days.


---

# 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.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-configure-data-storage-optimizer/pdso-hcp-configuration/hcp-tenant-configuration.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.
