Roles determine the tasks that users can perform. Roles can be grouped in the following ways:
Product-specific roles
Examples of Essbase Studio roles are cpAdmin and cpDM. The roles determine the type of interaction that the user can have with Essbase Studio artifacts. The interaction of each role with specific artifacts is described in the Essbase Studio Roles appendix in the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.
Shared Services roles
Examples of Shared Services roles are Project Manager or Provisioning Manager. Most Shared Services roles are global (the role applies to all Shared Services applications). For information on Shared Services roles, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide
The following Essbase Studio roles provide different levels of authority to perform tasks in Essbase Studio.
cpAdmin—Administrator; performs all Essbase Studio tasks, including deploys cubes and executing drill-through reports
cpDM—Data Modeler; performs all tasks related to metadata element creation and maintenance; deploys cubes; executes drill-through reports
cpDSAdmin—Data Source Administrator; performs all tasks related to data source connection creation and maintenance; executes drill-through reports
cpViewer—Viewer; views all Essbase Studio data sources and metadata elements; executes drill-through reports
Because the cpAdmin and cpDM users are responsible for deploying cubes to Essbase, they must be provisioned with these additional roles:
Shared Services Administrator (optional)
Shared Services Project Manager (required)
At a minimum, the Project Manager role is required to deploy cubes.
Essbase Administrator (optional)
Essbase Create/Delete Application (required)
When deploying cubes, information is written into Essbase; therefore, at a minimum, the Create/Delete Applications role is required in order to write to Essbase.
After cubes are deployed, you are not required to provision Essbase Studio users for access to the new Essbase applications and databases. Permissions are inherited for the cubes Essbase Studio deploys to Essbase. You may, however, have to provision Essbase users for access to applications and databases created in Essbase Studio