Premium
See what's included in Target Premium.

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. Refer to the sections below for more information about each task.

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, or tags in Adobe Experience Platform
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. In Adobe Target, click Administration > Properties > Assign Properties to Workspaces.

    Or

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

  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.

Step 1. Add users (Optional) section_A92AF0F921B743FEB9E9033433BD816A

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 the Users tab at the top of the page > Add Users to create new users or to edit existing users.
  2. Follow the instructions in Manage Users and Groups in the Experience Cloud in the Enterprise User Guide.

Step 2. Create a workspace (product profile) section_B82EB409B67C4D9D9D20CE30E48DB1DC

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 site section, or via any other method they choose.

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

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

    workspace

  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.

NOTE
See the training video below for more information about configuring workspaces.

Obtain your workspace ID workspace-id

You’ll need to pass the workspace ID to leverage Enterprise Permissions in Target APIs.

  1. In the Adobe Admin Console, click the Products tab, then click the product in the left menu to display the PLC(workspace) list.

  2. Click the desired PLC(workspace), then locate the “profiles” ID in the URL, as shown below.

    workspaceID

Step 3. Create user groups (Optional) section_5F5CB9AA7A9F4D26953E22016DA59605

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 the Users tab at the top of the page > 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.

Step 4. Create properties section_E8F2C92BE0F4466AB87604059C9CF3FD

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

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

Tip: See the training video below for more information about how to create properties.

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

  2. Click Create Property.

    Fill in the fields:

    • Property Name (Required): Specify a descriptive name for the property.
    • Description: Specify an optional description for the property.
    • Channel: Select the desired channel for the property: Web, Mobile App, Email, or Other/API (for example a set-top box or PlayStation console).
  3. Click Copy to copy the code to your clipboard that you’ll use while performing the steps in 5: Update Your Implementation to Include the at_property Parameter.

  4. Click Save when done.

NOTE
See the training video below for more information about creating properties.

Step 5: Update your implementation to include the at_property parameter section_9B17A59807A94712BE642942442EBBC8

To use the Target user-permissions functionality, you must add the at_property parameter to any call that is hitting Target (Target call, api call, 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 Administration > 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.

      Property hover code

    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 “Custom Parameter” in tags within Adobe Experience Platform:

      For more information, see Add Mbox Params in the Tags overview documentation.

    • Via the targetPageParamsAll() function: Place the following code in the <head> tags, above the at.js reference.

      code language-javascript
      <script>
       function targetPageParamsAll() {
        return {
         "at_property": "5f8bd98b-1456-a84c-2a96-11s9b8e2b112"
        };
       }
      </script>
      

      For more information about how to do this with at.js, see targetPageParamsAll.

Step 6: Specify roles and permissions section_8C425E43E5DD4111BBFC734A2B7ABC80

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

    Workspace

  2. Click the name of the desired profile (for example, Default Workspace).

    Default Workspace

  3. Click Users.

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

    configuration users

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

    Product Role drop-down list

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Role Description
    Approver Can create, edit, and activate or stop activities.
    Editor Can create and edit activities before they are live, but cannot approve the launch of an activity.
    Observer Can view activities, but cannot create or edit them.
    Publisher Similar to the Observer role (can view activities, but cannot create or edit them). However, the Publisher role has the additional permission to activate activities.

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

Training videos

The following videos contain more information about the concepts discussed in this article.

NOTE
The Target Administration menu UI (formerly Setup) has been redesigned to provide improved performance, reduce the maintenance time required when releasing new features, and to improve the user experience across the product. The information in the following videos is generally correct; however, options might be in slightly different locations. Updated videos will be posted soon.

How to Configure Adobe Target Workspaces (6:55) Tutorial badge

This video explains how to create workspaces.

  • 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

How to Create Properties in Adobe Target (3:05) Tutorial badge

  • 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
recommendation-more-help
3d9ad939-5908-4b30-aac1-a4ad253cd654