[premium]{class="badge informative"}

Understanding Enterprise User Permissions in Adobe Target


In this video, you learn how to:

  • Describe the three Adobe Target user levels
  • Understand properties and workspaces

Intended Audience

  • Administrator
Welcome to the Adobe Target Enterprise Permissions Overview. In this video, we will discuss how the new Enterprise Permissions workflow is designed to help you control the type of access that users have within your organization by way of three main concepts: user roles, properties, and workspaces.
By the end of this video, you will learn about the three role levels that Adobe Target users can hold, the concepts of Properties and Workspaces, and how these boundaries and groupings work together to allow for control over users’ access levels, and different examples of Properties for your organization to consider.
Across Adobe Target, there are three possible roles that a user can hold: observer, editor, and approver. The permissions and levels of access increase with each role designation. But let’s say that your organization has separate domains or apps that certain people need to manage more closely than others. Let’s even say that your organization is split by geographic region with offices in the US, France, and India, meaning that, naturally, each office would need more control over the marketing initiatives based in their locale. Now, admins can create properties to establish boundaries around where Users can run Target Activities. Properties can be implemented at any level. For example, across an entire domain, a mobile app, a set top box experience, and more. Once you’ve established all of your Properties, you’ll need to separate them into groups along with the specific Users that should have access to them. In Target, we refer to each of these groups as a workspace. In the Admin Console, these workspaces are called product profiles.
A workspace is a focused view of a common set of Properties, Activities, and Offers, all accessible by a set of specific Users with different roles. So let’s say, for example, that this User needs observer access but only to these three properties because none of her work involves the organization’s non-US apps or websites. Target admins can accomplish this by creating a workspace, including the corresponding Properties and adding Users. The roles assigned to these Users will apply to the entire workspace, and only these Users can access the audiences, offers, and activities created in this workspace. Because roles are assigned per workspace, a User may belong to multiple workspaces and hold a different role in each one. Likewise, a Property may be included in as many workspaces as needed. These features allow for a whole new level of flexibility when structuring user permissions in your organization.
For more details, check out our short step-by-step videos on how to create a Property in Adobe Target and how to configure workspaces in the Admin Console. Thank you.