Editing the Global security policy
If you can implement the security strategy for your organization with one security policy, use the Global security policy as your single policy. In most cases, you do not change the default permissions for the supplied Plan Administrator and Plan User system roles. Instead, you add new security roles to implement your security goals.
1.
Select Settings > Operações de Marketing Settings > Security Policy Settings > Global.
2.
Add the new security roles as follows:
a.
Click Add Another Role.
b.
Enter a name and description for the role.
c.
Repeat these steps for each role you add.
3.
Click Save and Edit Permissions. The Permissions page appears so that you can grant or block access to features for each role.
4.
From the Access to list, select the Plan object type and then use the check boxes to configure permission settings for each security role. You repeat this procedure for each object type listed by Access to.
*
You can use Shift + click to select multiple cells.
5.
For projects, perform these steps.
a.
Configure the Add Projects and View Project in the List permissions for each object and security role.
b.
Select a template. The security policy displays a column for each project role specified for this template on the Project Roles tab in the Team Members section. An access control section displays for each tab in the template.
c.
Configure permissions for each tab in the template, including the custom tabs, for the project, object, and security roles.
d.
Repeat steps b) and c) for each project template.
6.
For requests, perform these steps.
a.
Configure the Add Requests and View Request in the List permissions for each object and security role.
b.
Select a project template. The security policy displays a column for each project role specified for the template on the Project Roles tab in the Project Request Recipient section. An access control section displays for each tab in the template.
c.
Configure permissions for each tab in the template, including the custom tabs, for the project, object, and security roles. When configuring requests, remember that the permissions you set for the Request Recipient object role must match the permissions for at least one of the recipient project roles.
d.
Repeat steps b) and c) for each project template for which you want to configure custom permissions for requests.
7.
For marketing objects, be sure to configure permissions appropriately for each template.
8.
Click Save Changes when you are finished.
Copyright IBM Corporation 2013. All Rights Reserved.