Shared Projects in Tenant Partitioning

Strategy (August 2026) adds support for tenant partitioning within a single shared project.

See the following topic to use shared projects in a tenant-partitioned Strategy environment. A shared project allows users from multiple tenants to access the same project while keeping each tenant's content isolated.

Converting a project to a shared project is permanent. After you change a project from Global to Shared, you can not change it back to Global.

Shared projects require tenant partitioning to be enabled in the environment. For more information, see Tenant Partitioning

A shared project is a project available to all tenants in a tenant-partitioned environment. It provides a common project space where tenants can use shared content while continuing to create and manage their own tenant-specific content.

Use a shared project when your organization wants to provide the same project experience, dashboards, folders, reports, or other content to multiple tenants without creating a separate copy of the project for each tenant.

See the following sections on shared projects in tenant partitioning:

How Shared Projects Work

  • A shared project starts as a global project.

  • A global administrator converts the project to Shared.

  • After conversion, users from all tenants can access the project, subject to their privileges and security roles.

  • Content created by a tenant user in the shared project belongs to that user's tenant.

  • Tenant users can see shared global content and content from their own tenant, but they can not see content owned by other tenants.

When to Use a Shared Project

Shared projects are useful when you want a common project foundation multiple isolated tenants.

Scenario Example
You want tenants to use the same project shell. An OEM deployment provides the same analytics application to many customer tenants.

You want to publish common content once.

Global administrators publish baseline dashboards, reports, folders, or metrics that all tenants can run.
You want tenant users to create their own content in the same project. Each tenant creates its own dashboards or reports without exposing them to other tenants.

You want to reduce project duplication.

Instead of maintaining one similar project per tenant, administrators maintain one shared project.

Prerequisites

  • Tenant partitioning must be enabled for the environment.

  • Only a global project can be converted to a shared project.

  • You must have global administrator privileges.

  • Back up and verify your metadata repository before enabling tenant partitioning or converting important projects.

Plan carefully: Shared project conversion can not be undone and you can not limit a shared project to select tenants. You can restrict project access through security roles.

Enable a Shared Project in Workstation

  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 Projects.

  4. Right-click a global project and click Properties.

  5. Next to Tenant, select Shared.

  6. Click OK.

  7. Review and accept the warning.

    Now that the project is saved as Shared, tenant users can access the project according to their security role settings for the project.

How to Use a Shared Project

Global Administrators and Users

Global users can access and administer shared projects according to their privileges and object permissions. Global users can create, save, delete, and manage global content in the shared project where they have permission. They can also modify, delete, and manage tenant content as long as they have permission.

When a global user creates an object in a shared project, the object is a global object.

Tenant Users

Tenant users can use a shared project, but their access is tenant-aware and restricted.

Tenant User Action Supported? Behavior
Access a shared project Yes Tenant users can access shared projects when they have the required roles and permissions.

Access a non-shared global project

No

Tenant users cannot access global projects unless the project is shared.
Use or copy existing shared objects Yes Tenant users can run shared global content when permissions allow.

Edit or delete existing shared objects

No

Tenant users can use shared global content but cannot modify or delete it.
Use shared objects across tenants Yes Shared objects without tenant-specific information are visible to all tenants, if their ACL permits so.

Use out-of-the-box folders

Yes

Out-of-the-box folders, such as Public Objects and Schema Objects, are shared by all tenants; their names and ACLs cannot be customized per tenant.
Create objects Yes Tenant-created objects belong to that tenant. Users can create content in a personal folder or, where permitted, in a shared folder accessible to users from the same tenant.

Save shared objects to a personal folder

Yes

Tenant users can save shared objects as copies in their own folder.
Edit or delete their tenant’s objects Yes Tenant users can manage content owned by their tenant when permissions allow.

View or manage another tenant’s objects

No

Tenant isolation prevents tenant users from accessing other tenants’ content.
Create or modify tenant-level schema objects No Schema administration remains controlled by global administrators; tenant users cannot modify shared schema, or create project schema objects likes Attributes, etc.

Import tenant-level objects into another project

Partially

Supported for the same tenant’s tenant-exclusive project or a shared project; not supported for another tenant’s tenant-exclusive project or a global project.
Duplicate a shared project No Tenant administrators cannot duplicate a shared project.

Customize shared project settings

No

Project-level settings are shared and cannot be customized per tenant.
View and generate project documentation Yes Tenant administrators can view project documentation (only the subset of accessible objects).

Hide tenant objects from global administrators

No

Tenant objects cannot be hidden from global administrators, who retain bypass privileges.

Object Visibility and Ownership

Shared projects can contain both global content and tenant-owned content.

Global Content

Global content is created by global users. Tenant users can view or use global configuration objects when permissions allow, but tenant users can not edit or delete those global objects.

Tenant-owned Content

Content created by a tenant user in a shared project belongs to that tenant. It is visible to the following:

  • Users from the same tenant.

  • Global administrators.

It is not visible to users from other tenants.

Duplicate-name Behavior

When users create or duplicate objects in a shared project, Strategy checks for name conflicts against global (shared) objects and objects in the same tenant. Objects in different tenants can use the same name when tenant isolation allows it, under the same folder.

Search Behavior

Search results in a shared project respect tenant isolation.

Global users can search global objects and tenant-owned objects in the shared project, subject to permissions.

Tenant users can search global objects and objects from the same tenant. Objects from other tenants are not shown.