CentraSite Documentation : CentraSite User’s Guide : Using the Asset Catalog : Setting Permissions on an Asset : Assigning Permissions Using the User Interface : Setting Instance Level Permissions on an Asset
Setting Instance Level Permissions on an Asset
Use the following procedure to set instance-level permissions on an asset using CentraSite Control:
Important:  
CentraSite Control does not allow you to set permissions on asset instances of the type: REST Service, OData Service, XML Service, Virtual REST Service, Virtual OData Service, and Virtual XML Service. CentraSite Control allows you to set permissions on asset instances of type: Service and Virtual Service.
To assign permissions to an asset
1. Display the details page for the asset whose permissions you want to edit. If you need procedures for this step, Viewing Details for an Asset.
2. Open the Permissions profile.
3. To add users or groups to the Users and Groups list, do the following:
a. Click Add Users and Groups.
Note:  
This button is only selectable if you have the Modify permission on the asset and also the Modify permission on the asset's Permission profile. For details, see Who Can Set Permissions on an Asset? and Restricting Access to Specific Profiles.
b. Select the users and groups to which you want to assign permissions.
If you want to filter the list, type a partial string in the Search field. CentraSite applies the filter to the Users/Groups column.
Examples
String
Description
b
Displays names that contain b
bar
Displays names that contain bar
%
Displays all users and groups
c. Click OK.
4. Use the View, Modify and Full check boxes to assign specific permissions to each user and/or group in the Users and Groups list as follows:
Permission
Allows the selected user or group to...
View
View the asset.
Modify
View and edit the asset.
Full
View, edit, and delete the asset. This permission also allows the selected user or group to assign instance-level permissions to the asset.
5. When you assign instance-level permissions on an asset, the related objects (for example, bindings, operations, interfaces, and so on.) receive the same permissions that are assigned on the asset.
6. If you want to ensure that the asset's dependent objects (for example, a WSDL or schema) receive the same permissions, mark the checkbox Propagate permissions to dependent objects. If you do not mark this checkbox, the permissions of the dependent objects will not be modified.
In addition, you can ensure that the dependent objects of the same object type receive the same profile permissions. To do this, mark the checkbox Propagate profile permissions.
For more information about propagation of permissions and propagation of profile permissions, see Propagation of Permissions.
7. Click Save to save the new permission settings.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback