About security policies
Security policies are the "rule books" that govern security in IBM® Campaign; they are consulted each time a user performs an action in the application. Security policies are created per partition. There is no sharing of security policies across partitions. Each partition in IBM® Campaign can have multiple security policies.
A security policy consists of multiple roles that you define. Each role contains a set of permissions that determine the actions users can perform and the objects that they can access. You can assign users to a role directly, or assign groups to a role (users in those groups would be assigned the role).
When you create an object such as a campaign or offer in the top-level folder, you apply a security policy to the object. In addition, when you create a top-level folder, you apply a security policy to the folder, and any objects or subfolders you create within that folder inherit the security policy that you applied to the folder.
Applying security policies to objects or folders allows you to separate the objects in IBM® Campaign for use by different groups of users. For example, you could configure your security policies so that users belonging to one policy cannot access or even view objects that are associated with other policies.
You can create your own security policies or use the default global security policy included with IBM® Campaign.
The global security policy
How Campaign evaluates permissions
Using the Owner and Folder Owner roles
Guidelines for designing security policies
Copyright IBM Corporation 2015. All Rights Reserved.