Page Comparison

{scrollbar}

----
Besides defining access and restrictions on cubes, it may be necessary to define permission on the different analytic components saved in the server as well. *O3 Server Administrator* lets you assign permissions on: Scorecards, Models, Rules, Actions, Desktops, Queries, Dashboards, Reports, Simulations and Expressions.
{quote}
(!) Note
The managing of permissions on views differs from these components due to the required integration with cubes and the way in which users can continuously create, improve and share the views.
{quote}

h2. Assigning permissions to Components

On Scorecards, Models, Rules, Actions, Desktops, Queries, Dashboards, Reports, Simulations and Expressions, access definitions and restrictions are applied on the cubes they use, but it may be necessary, for instance, to restrict users so they cannot modify or see certain components. 

Permissions to _Read, Write and List_ can be assigned on these components. In the same way as for cubes, the assignment of these permissions is performed on the roles and users playing each role acquire the permissions indirectly. It is relevant to bear in mind that permissions can only be assigned to those components saved in O3 Server.

The following picture shows the tab where permissions are assigned, in the Properties Pane of the Security branch in *{_}O3 Server Administrator{_}*

!O3ServerAdministrator-Security-Permissions.png|align=center!\\

It is also possible to assign permissions on components to a role in a general or particular way. For instance, you may assign permissions to a role  to _Read_ all defined desktops by default, and only assign permissions to _Write_ on a certain desktop for users to improve it.

In order to assign permissions in general, the first item in the list of components is always _Repository_. This special item does not correspond to any specific component and is used to assign permissions inherited by the remaining components of the list by default.

By default, when a component is first saved in O3 Server, it inherits the permissions to _Read, Write and List _ defined in the first _Repository_ item of each role.

In turn, also by default, this _Repository_ item is configured with the _Inherit_ value, which means that all users playing the role will have full permissions on the components of the selected type.

To assign permission on components to a role:
# Start O3 Server Administrator.
# Expand the Services \| Security branch in the Administration Tree.
# Click on the _Permissions_ tab in the Properties Pane. This tab displays a list with the defined roles on the right and an area for the assignment of permissions.
# Select the role to which you wish to assign permissions from the list.
# Select the type of component on which you wish to assign permissions from the _Component_ drop-down list in the _Permissions_ area. This area also displays a list of the components of the selected type saved in O3 Server, plus the Repository item to assign permissions in a general way.
# Select the component on which you wish to assign permissions from the drop-down list.
# To assign permissions on the selected component of the list it is necessary to change the values of the _Read, Write and List_ columns.
Values are indicated independently, and by default each component is configured with the Inherit values.
The available values to assign permissions are:
#* Deny. Users playing the selected role will be denied the permission corresponding to the column. 
#* Allow. Users will have the permission corresponding to the column. 
#* Inherit. Permission will be determined by the value of the first item on the list, _Repository_.
The way to assign permissions  to a certain role on all the components is by assigning the Inherit value.  
#* Click on the Apply button in the Permissions area to confirm changes to permissions.
When you change a permission, the list of roles and the frame to select the type of component are automatically disabled until the performed change is applied or canceled. 

h2. Managing Permissions on Views
{note:title=Note}
Under construction {note}

----
{children}