Hi
We have created 2 additional Portals, one for all users and one for those we want to have access to more powerful Views and Editors for updating
How can we easily set up security at the top level , so that users can be restricted from seeing the more powerful Portal?
Thanks for any guidance
Rob
User access to specific Portals
-
jonathan.carter
- Posts: 1087
- Joined: 04 Feb 2009, 15:44
Hi Rob,
You can control who can see which Portals by using the Security Classifications to classify those new Portals that you have defined. In that way, only those users who have clearance for the classifications that you have defined will see those Portals.
First thing to note is that the Security Classifications are defined in an Essential repository.
Start by defining a new Security Group and define at least one level in that group. With the group defined, you can now classify the Portal(s) to which you wish to limit access.
To classify a Portal, go into the repository and navigate to the Portal instance and add your new Security Classification to the "System Security Read Classification" slot. You should probably also specify the Edit classification slot, too but the Viewer only uses the Read classification, currently. (NOTE, Editors and the repository browser use both Edit and Read).
These changes won't take effect until you publish your repository to your target Viewer. Before you do that, go to the Configure -> Repository Administration -> Manage Repository Users, select your account and select your Edit Clearance and Read Clearance Levels so that you will be able to see the Portal.
You can multi-select the users to whom you want to provide access to the new Portals and select the required Edit and Read clearance for them. Any user without this clearance will not be able to access the Portal.
Publish your configured repository to the Viewer for the security to be applied.
This video on how to classify views and elements demonstrates the above concepts.
Jonathan
You can control who can see which Portals by using the Security Classifications to classify those new Portals that you have defined. In that way, only those users who have clearance for the classifications that you have defined will see those Portals.
First thing to note is that the Security Classifications are defined in an Essential repository.
Start by defining a new Security Group and define at least one level in that group. With the group defined, you can now classify the Portal(s) to which you wish to limit access.
To classify a Portal, go into the repository and navigate to the Portal instance and add your new Security Classification to the "System Security Read Classification" slot. You should probably also specify the Edit classification slot, too but the Viewer only uses the Read classification, currently. (NOTE, Editors and the repository browser use both Edit and Read).
These changes won't take effect until you publish your repository to your target Viewer. Before you do that, go to the Configure -> Repository Administration -> Manage Repository Users, select your account and select your Edit Clearance and Read Clearance Levels so that you will be able to see the Portal.
You can multi-select the users to whom you want to provide access to the new Portals and select the required Edit and Read clearance for them. Any user without this clearance will not be able to access the Portal.
Publish your configured repository to the Viewer for the security to be applied.
This video on how to classify views and elements demonstrates the above concepts.
Jonathan
Essential Project Team
