Strategy One

Platform Analytics Support for Multi-tenant Metadata

Strategy One (May 2026) adds support for Platform Analytics in your multi-tenant metadata.

Enable Platform Analytics Support

To enable Platform Analytics support for multi-tenancy, you must perform a manual API call to a telemetry endpoint.

  1. Call POST /api/telemetry/admin/multitenantMetadata/enable.

    A successful response displays status 202 and includes "status": "IN_PROGRESS" in the body.

  2. To check the process status, call GET /api/telemetry/admin/multitenantMetadata/status.

To access the API documentation, use the following template, replace <environment host> with your environment details: <environment host>/MicroStrategyLibrary/api-docs/index.html?visibility=all#/Telemetry

To enable multi-tenant support for Platform Analytics, you must alter the table and it will fail is there are other long-running queries on the table. If the enabling process fails, try again later when the table is not busy.

Data Security

The following topic assumes the tenant administrator has all privileges besides the Create and manage tenants privilege. Therefore, the administrator can see all global users and other global resources such as data sources and license.

  • The data from all tenants resides within the same platform_analytics_wh schema. Data security is enforced using row-level access controls lists of PostgreSQL. For all tables that are tenant-level, the row-level security ensures no data leaks across tenants.

  • Because tenant administrators have access to all data sources, they have access to all global data not protected by row-level access control lists, such as license telemetry data.

  • Global administrators should never publish a cube or execute a report with caching enabled in a tenant-level Platform Analytics project. As global administrators are allowed to see data for all tenants, publishing a cube or executing a report with caching enabled could result in a data leak.

  • To avoid exposing global data that is not related to tenants, the following objects are not available in the Platform Analytics project:

    Dashboard

    • Admin Setting Change History

    • Auto Adoption

    • Compliance Telemetry

    • Database Capacity Planning

    • Intelligence Center Dashboard

    • Remote Diagnostic

    Cube

    • Admin Setting Change Cube

    • Auto Enabled Users

    • Capacity Planning

    • Compliance Telemetry

    Attribute

    • /Schema Object/Attributes/A11. Compliance Telemetry

    Filter

    • Auto Enabled Users

    • Auto Privilege Enabled Users

Create a Tenant

Enable Tenants

  1. Open the Workstation window.

  2. Log in to your environment as a global user with the Create and manage tenants privilege.

  3. In the Navigation pane, click Environments.

  4. Right-click your environment and choose Enable Tenant-based Object Isolation.

  5. Review and accept the warning.

  6. Reconnect to your environment.

  7. Right-click your environment and ensure Multi-tenancy Enabled displays.

Create a Tenant

  1. Click, , next to Tenants.

  2. Type a Name for the tenant.

  3. In the left pane, click Users and Groups.

  4. Select the check box next to the Users and Groups you want to add to the tenant.

  5. In the left pane, click Project Access.

  6. Select the check box next to the Projects you want to add to the tenant.

  7. Click Save.

Create a Platform Analytics Project for Each Tenant

  1. Note the tenant name.

  2. In Navigation pane, click Scripts.

  3. Right-click the Create Tenant PA Project script and click Run.

    The script enables granular control of HTML and JavaScript content, because it is required for migrating objects to tenant Platform Analytics projects.

    Available variables:

    • pa_name: Name of the new Platform Analytics project to create.

    • global_pa_name (Optional): Name of the global Platform Analytics project. Default to Platform Analytics, if not provided.

    • tenant_name (Optional): Name of a tenant if the user wants to assign the new project immediately. The project will not be assigned to a tenant if not provided.

  4. Optionally assign the project to a tenant. You do not need to complete this step if you provided a tenant ID when running the Create Tenant PA Project script.

  5. To create subscriptions to automatically update data in the new Platform Analytics project, right-click the Subscribe to PA Data script and click Run.

    Available variables:

    • pa_name (Optional): The project name of the Platform Analytics project. If the variable is empty, it defaults to Platform Analytics for the global Platform Analytics project. For the tenant Platform Analytics project, the user should always provide the project name.

    • tenant_admin_id (Optional): The user ID of the tenant administrator. This variable is required for the tenant Platform Analytics project. If the variable is empty, it defaults to the user who executes the script, which should be the global administrator.

      The Activity tab in Properties uses data from the global Platform Analytics project.

      Any project can only be assigned once from global to a tenant. This operation is irreversible. A project can not change its tenant. Consider backing up your environment before performing this action.

Upgrade the Platform Analytics Project Schema

  1. In the Navigation pane, click Tenants.

  2. Right-click your tenant and choose Properties.

  3. Highlight and copy the tenant ID and close the properties.

  4. In the Navigation pane, click Scripts.

  5. Right-click the Upgrade Tenant PA Project script and choose Run.

    This script creates a new Platform Analytics project, migrates objects from the global Platform Analytics project, and assigns it to a tenant.

    Available variables:

    • global_pa_name (Optional): The project name of the global Platform Analytics project. If this variable is empty, the default value is Platform Analytics.

    • pa_names (Optional): Comma-separated project names of the Platform Analytics projects to upgrade. If this variable is empty, it will upgrade all tenant-level Platform Analytics projects.

Platform Analytics Functionality with Multi-tenancy

  • Global administrators should have access to all Platform Analytics data for global and all tenants.

  • Tenant administrators should only have access to Platform Analytics data that's available in their tenant.

  • There are global objects (for example, schedules) shared by all tenants. Tenant administrators will see all records for these global objects. Tenant administrators can also see a full list of those objects. However, tenant administrators will only see activities related to their tenant.

Known Limitations

  • The multi-tenant feature can not be turned off once you turn it on.

  • Any project can only be assigned from global to a tenant once. The assignment cannot be reverted or changed.

  • If you perform activities on Web, it will not have tenant information. Global administrators can view the activities but the tenant can not.

  • Server-level objects (for example, users) are global and the Platform Analytics data is shared to all tenants by default. If you have an object that should not be shared to tenants, global administrators should create a tenant and assign them to the tenant.

  • The API call that enables multi-tenancy support for Platform Analytics can fail if there are other long-running queries on the tables. If the API call fails, the user should retry the API after the long running queries are busy or after querying the warehouse database. The user should then check if there are locks on the failed tables.