Configure Enterprise Permissions

Information about the tasks required to add users to your Target implementation; create workspaces, user groups, and properties; update your Target implementation to include the at_property parameter; and specify roles and permissions.

Note: Properties and Permissions functionality is available as part of the Target Premium solution. They are not available in Target Standard without a Target Premium license.

The following table lists the tasks you should perform to create properties and assign user roles and permissions:

Task Performed In

1. Add Users (Optional)

Adobe Admin Console for Enterprise

2. Create a Workspace (Product Profile)

Adobe Admin Console for Enterprise

3. Create User Groups (Optional)

Adobe Admin Console for Enterprise

4. Create Properties

Target UI

5: Update Your Implementation to Include the at_property Parameter

Target UI / at.js functions / Dynamic Tag Management

6: Specify Roles and Permissions

Adobe Admin Console for Enterprise

For those tasks performed in the Adobe Admin Console for Enterprise, access the console by following these steps:

  1. Go to https://adminconsole.adobe.com/enterprise/ > sign in using your Adobe ID, if you have not already logged in.

    Or

    If you are already logged in to the Marketing Cloud, go to http://www.marketing.adobe.com, then click the App icon ( ) in the top navigation bar > click Administration on the right side > then click Launch Admin Console.

  2. (Conditional) If you have access to the Admin Console for Enterprise for more than one organization, click the user avatar in the right corner or the top navigation bar, then select the desired organization.

1. Add Users (Optional)

When you start using the new Properties functionality, all user management must be performed in the Adobe Admin Console for Enterprise. However, all of your existing users in Target will be migrated from Target to the Admin Console for Enterprise.

  1. In the Admin Console, click User Management > Users to create new users or to edit existing users.

  2. Follow the instructions in Manage Users and Groups in the Marketing Cloud in the Enterprise User Guide.

2. Create a Workspace (Product Profile)

A workspace (Product Profile) lets an organization assign a specific set of users to a specific set of properties. In many ways, a workspace is similar to a report suite in Analytics.

Organizations can begin taking advantage of Enterprise permissions functionality by creating new workspaces within Admin Console, assigning Target properties to these workspaces, and moving users from the "Default Workspace" configuration to these newer, limited-access workspaces.

Customers can use these workspaces to separate access to different teams by region, by business unit, by sight section, or via any other method they choose.

Users can be part of multiple workspaces and can even have different roles within each workspace.

This video explains how to create workspaces:

How to Configure Target Workspaces 6:55

  • Access the Adobe Admin Console from the Adobe Target interface (3 ways)

  • Configure a workspace in Adobe Admin Console

    • Add users to workspaces

    • Add properties to workspaces

  • Understand default workspaces

  1. In the Admin Console, click Products, then select the name of the desired product.

  2. Create the desired workspace (Product Profile):

    • Default Access: All existing activities will be merged into a single project called "Default Access." This will have no impact on customers. All user roles and functionality will remain exactly the same as they are prior to this change.

      All activities created via Adobe Experience Manager (AEM), Adobe Mobile Services, and Target Classic will also be part of the "Default Access" workspace. You cannot currently move projects from "Default Access" to another project.

    • New workspaces (Product Profiles): You can begin taking advantage of the new permissions functionality by doing the following:

      • Creating new workspaces within the Admin Console for Enterprise.

      • Assigning Target properties to the workspaces.

    You can use these workspaces to divide access to different teams by region, business unit, site section, or via any other method you choose. Users can be part of multiple workspaces and can have different roles within each workspace.

  3. Follow the instructions in Create and Manage Product Configurations in the Enterprise User Guide.

3. Create User Groups (Optional)

You can create user groups, such as Developers, Analysts, Marketers, Executives, etc., and then assign privileges across multiple Adobe products and workspaces. Assigning a new team member all the appropriate privileges across different Adobe products can be as easy as adding them to a specific user group.

  1. In the Admin Console, click User Management > User Groups to create new user groups or to edit existing groups.

  2. Follow the instructions in Manage Users and Groups of a Product Configuration in the Enterprise User Guide.

4. Create Properties

This video explains how to create properties:

How to Create Properties 3:05

  • How to create a property within the Adobe Target interface

  • How to generate a property token to include in your property implementation

  • Familiarize yourself with the three implementation methods:

    • Web

    • Mobile app

    • Email, set top box, or API calls

Properties are enabled by adding a specific name/value pair as a parameter with any call (mbox, api, etc.) to Target.

Properties belong to specific channels (Web, Mobile, Email, and API/Other).

  1. In Target, click Setup > Properties to display the Properties list.

  2. Click Create Property.

    Fill in the fields:

    • Channel: Specify the desired channel for the property: Web, Mobile App, Email, or Other/API (for example a set-top box or PlayStation console).

    • Name (Required): Specify a descriptive name for the property.

    • Description: Specify an optional description for the property.

  3. Click Generate Code to generate the code you'll use while performing the steps in 5: Update Your Implementation to Include the at_property Parameter.

  4. Copy the code to your clipboard.

  5. Click Save when done.

5: Update Your Implementation to Include the at_property Parameter

To use the Target user-permissions functionality, you must add the at_property parameter to any call that is hitting Target (mbox, api, etc.).

To obtain the at_property parameter code:

  1. (Conditional) Use the implementation code you generated and saved to your clipboard while performing the steps in 4. Create Properties and proceed to Step 2.

    Or

    In Target, click Setup > Properties to display the Properties list.

    1. Hover your mouse pointer over the Last Updated column for the desired property to display and click the Code icon ( ).

    2. Right-click the highlighted implementation code to copy it to your clipboard.

  2. Update your Target implementation with the implementation code obtained in the previous step.

    There are several ways to update your Target implementation. For example, the following methods can be used for web pages:

    • Via a "Global Parameter" in Dynamic Tag Management (Adobe Activation):

      For more information, see Global Parameters - Adobe Target in the Dynamic Tag Management Product Documentation.

    • Via the targetPageParams() function: Place the following code in the <body> tags, above the at.js or mbox.js reference.

      For more information about how to do this with at.js, see targetPageParams().

    • Via the mboxCreate() function:

      For more information about how to do this with at.js, see targetPageParams().mboxCreate(mbox,params)

6: Specify Roles and Permissions

  1. In the Admin Console, click Products, then select the name of the desired product.

    Note: The Properties and Permissions functionality applies to Target Standard/Premium only. You cannot use this functionality with Target Classic.
  2. Click the name of the desired profile.

  3. Click Configuration Users.

    The Configuration Users tab displays all of the users in that workspace.

  4. Select the desired permissions role (Approver, Editor, or Observer) by using the drop-down list for each user in the Product Role column.

    Role Description

    Observer

    Can view activities, but cannot create or edit them.

    Editor

    Can create and edit activities before they are live, but cannot approve the launch of an activity.

    Approver

    Can create, edit, and activate or stop activities.

    For more information, see Manage Product Permissions and Roles in the Admin Console in the Enterprise User Guide.