You can control access to decision service branches by enforcing security for projects in
releases, activities, or ungoverned branches. You can also control access to these projects for
specific groups of users.
About this task
When you enforce security within a decision service, you can control which groups of users have
access to projects in the different branches. For example, you can enforce security for an entire
decision service, and select groups that can access this decision service. You can then restrict
access for a specific project, so that among these groups, only some groups can access this
project.
Security is inherited from a branch. For example, when a new project is added to a release that
inherited security from the original release, the project gets the inherited security of its
release.
You define which users are members of a group in the tab Groups.
Procedure
-
Log in to the Business console as a Decision Center administrator.
-
In the Administration tab, click Project
security. In this tab, you have a tree grid view of the decision services. You can
expand each decision service and their branches, to see the projects in each branch.
-
Hover over the branch for which you want to enforce security, and click the icon to
edit it.
-
In the window that opens, a status under Security indicates whether the
security is enforced or not. Click this status to modify the state of the security.
Note: If the parent branch already has security enforced, the security settings are inherited from
this branch. You can click the message Security settings are inherited from
Branch to override the security settings.
-
For branches on which security is enforced, select the groups of users who can access the
branch in the Groups section.
- Optional:
After you enforce security in a branch, you can restrict access to some projects in this branch
for specific groups of users. Click the Edit icon for your project, and select the groups that can
access this project.
-
Click Done to save your changes.