System Administrator Scenarios › How to Set Up Partitions › Plan the Implementation

Plan the Implementation

To work with partition models and partitions, you need the following access rights:

• Administration - Studio
• Administration - Partition Models

Before you start setting up partitions, determine the following information:

• The number of partitions needed
• The hierarchical structure of the partitions
• What to include in each partition
• Users for each partition

As you plan, consider the following rules for working with partition models and partitions:

• You can set up multiple partition models.
• You cannot delete a partition model; however, you can deactivate it.
• An object can be assigned to only one partition model at a time.
• When you include a partition in a partition model, its location in the hierarchy is fixed. You cannot move the partition.
• A child partition can inherit what can be viewed in its parent, depending on the association mode selected. If the child partition has been modified, changes to the parent partition are not applied to the child partition.
• When an object is assigned to a partition model, its associations (for example, attributes, views, or links) are visible to all partitions in the partition model by default.
• A user who is not a member of any partition sees the default System partition views.
• A user with Studio access rights can be a member of more than one partition within a partition model. However, when the user creates an object, the user selects the partition to use. For example, a user can be a member of the U.S. and European partitions, but the user selects one partition to use when creating a project.
• Users can be assigned only one partition and therefore do not need to select a partition.

Back to Top