Home
Administrator Guides
Administrator Guide
Security in Unica Campaign
Security policies control user access to the objects and features in Unica Campaign.
The global security policy
Unica Campaign includes a default global security policy. You cannot delete this policy; it always applies. However, you can customize your security scheme as follows.

Administrator Guides
- Administrator Guide
  - Unica Campaign administration overview
    The Settings menu provides access to most of the tasks that Unica Campaign administrators typically perform.
  - Security in Unica Campaign
    Security policies control user access to the objects and features in Unica Campaign.
    - How security policies work
      Security policies are the "rule books" that govern security for folders and objects in Unica Campaign. They are consulted each time a user performs an action in the application.
    - The global security policy
      Unica Campaign includes a default global security policy. You cannot delete this policy; it always applies. However, you can customize your security scheme as follows.
    - How users are assigned to roles and security policies
      Unlike objects and folders, which are assigned to security policies as a whole, users are assigned to roles within security policies.
    - The Owner and Folder Owner roles in security policies
      The Owner and Folder Owner roles exist in the global policy and they are also created by default when you create a custom security policy. These roles automatically apply to all users who have been made members of a security policy by being explicitly assigned to any other role within that policy.
    - Definitions of permission states
      For each role, you can specify which permissions are granted, not granted, or denied. You set these permissions on the Settings > User roles and permissions page.
    - Guidelines for designing security policies
      Follow these guidelines when designing security policies for Unica Campaign.
    - How Unica Campaign evaluates permissions
      When a user performs a task or tries to access an object, Unica Campaign performs the following steps.
    - Security scenarios
      This section provides security policy examples and explains how they can be used to address common security needs.
    - Implementing security policies
      You can create and delete security policies in Unica Campaign and apply security policies to folders and objects.
    - Reference: Administrative permissions in Unica Campaign
      For each partition, you can assign administrative permissions to determine feature access by role. For example, you can allow the Design role to view flowchart logs but not clear the logs.
    - Windows impersonation administration
      Windows™ impersonation is a mechanism that allows Unica Campaign administrators to associate Unica Campaign users with Windows users, so that Unica Campaign processes invoked by an Unica Campaign user run under the credentials of the corresponding Windows user.
    - How Unica Campaign uses data filters to restrict access to customer data
      Administrators can define data filters in Unica Platform to restrict Unica users from accessing specific customer data. In Unica Campaign, data filters affect flowchart output.
  - Database table administration
    Unica Campaign administrators must perform initial one-time tasks and routine administration tasks that pertain to database tables.
  - Customizing campaigns
    Administrators can customize campaigns by using custom campaign attributes, initiatives, and products.
  - Offer template concepts
    Before administrators perform offer template management tasks, there are several important concepts to understand.
  - About audience level administration
    Unica Campaign is delivered with a single audience level called Customer. You can define any additional audience levels that you need. Audience levels let flowchart designers target specific groups, such as Households, in marketing campaigns.
  - Before you begin working with contact history
    Contact history is stored in the Unica Campaign system database in separate tables by audience level. Therefore, you need to set up audience levels before you begin working with contact history.
  - Response history administration
    Before you begin working with response history, you should read the audience level administration topics and set up required audience levels.
  - Monitoring and controlling flowchart runs
    Choose Campaign > Monitoring and use the All monitored runs page to view the status of all active flowcharts and suspend, resume, or stop flowchart runs.
  - Dimension hierarchy concepts
    A dimension hierarchy is a data construct that groups data into bins based on value ranges. Dimension hierarchies are the basis for a variety of reports.
  - Triggers administration
    Unica Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
  - Unica Campaign log files
    Unica Campaign records information in several different log files.
  - JVM Parameters
  - About codes in Unica Campaign
    Each campaign, cell, offer, and treatment in Unica Campaign has an identifying code that is generated by code generators, and conforms to a specified format.
  - Accessing the Advanced settings
    When a flowchart is open for editing, administrators can choose the Advanced settings option on the Admin menu to make administrative changes that affect only the current flowchart.
  - Unica Campaign integration with other products
    Unica Campaign optionally integrates with a number of other products.
  - Unica Campaign listeners
    The listener is a key component of Unica Campaign. It provides an interface between front-end clients and back-end analytical server processes.
  - Unica Campaign utilities
    Administrators use the Unica Campaign utilities to manage listeners, sessions, and flowcharts, and perform other important administrative tasks.
  - Configuring the ACOOptAdmin tool
    Configure the ACOOptAdmin tool to run Unica Optimize sessions from the command line.
  - Non-ASCII data in Unica Campaign
    Unica Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the application.
  - Configuration properties for Unica Campaign
    The configuration properties of Unica Campaign are located at SettingsConfiguration. For more details on the configuration properties, see the Campaign Administrator Guide.
  - About special characters
    Some special characters are not supported in any Unica Campaign object names. In addition, some objects have specific naming restrictions.
  - Introduction to character encodings
    This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Unica Campaign.
  - About Unica Campaign Error Codes
    Unica Campaign notifies users of error events when they occur with error messages that consist of a code number and error text.
  - Troubleshooting
- System Tables

The global security policy

Unica Campaign includes a default global security policy. You cannot delete this policy; it always applies. However, you can customize your security scheme as follows.

Modify the roles and permissions in the global policy to suit the needs of your organization.
Create custom policies and assign users only to your custom policies rather than the global policy.
Use both custom policies and the global policy.

Any custom policy you create exists under the global policy. If you choose not to create your own security policies, the global security policy is applied by default to the folders and objects that users create in Unica Campaign.

The global security policy contains six pre-defined roles You cannot delete the pre-defined roles, but you can modify their permissions.

The pre-defined roles in the global security policy are:

Folder Owner - All permissions enabled for the folders a user has created. All users have this role; you do not need to assign users to it.
Owner - All permissions enabled for the objects a user has created. All users have this role; you do not need to assign users to it.
Admin - All permissions enabled. The default user asm_admin has this role.
Execute - All permissions enabled.
Design - Read and write permissions on all objects. This role cannot schedule flowcharts or sessions.
Review - Read-only permissions.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.