Skip to content
Last updated

How Authentications Permissions Affect Activations in the Audience Studio

Authentications permissions affect what actions are available in the Create Activations and Edit Activations dialogs. Learn how to access these settings in Setting Policy-based Audience Studio Permissions Using TD Console.

PermissionsActivations in Audience Studio
  • Authentications: Full
  • Sources: Full or None

The user can create, copy, edit, run, and delete activations.

  • Authentications: View
  • Sources: Full or None

The user can view all authentications. The user cannot create, update, or delete authentications.

  • Authentications: Limited
  • Sources: Full or None

Manage Own Authentications : A user can view, use, edit, and delete any authentication created by this user.

Allow View for Specific Authentications : A user can view and use selected authentications as specified in the drop-down box.

  • Authentications: None
  • Sources: Full or None

The user can't create activation and receives an error message.

Users can't access authentications in the drop-down menu in the edit activations window, even if they have full control of that folder.

Activations Matrix

A user's access to activations depends on the master segment owner’s authentication permissions and their own authentication access combined. For example, in a case where the master segment owner has no authentications permissions, even a user with full authentications permissions will not be allowed to create, edit, run, or delete an activation for that master segment.

ActionOwner + User PermissionsUser Access

Create Activation

Owner - Authentication: View or Full

User - Authentication: View

User can create activations.

Create Activation

Owner - Authentication: Manage Own Authentication

User - Authentication: View

User can create activations for which they have received access.

Create Activation
  • Owner - Authentication: Allow View for Specific Authentications
  • User - Authentication
User can create activations for which they have received access.
Create Activation
  • Owner - Authentication: None
  • User - Authentication: View
UI prevents user from creating activation if Owner authentication permissions is none.

Create Activation

  • Owner - Authentication: None
  • User - Authentication: None

Known issue: UI allows the user to view the activation in the right-side panel after receiving the Cannot Create Activation error message.

Neither can view existing or create an activation and receives an error message.

View Activation
  • Owner - Authentication: View or Full
  • User - Authentication: View
Authentication icon is displayed
View Activation
  • Owner - Authentication: View or Full
  • User - Authentication: None
Authentication icon is hidden
Edit Activation
  • Owner - Authentication: View or Full
  • User - Authentication: View
Authentication fields are displayed
Edit Activation
  • Owner - Authentication: View or Full
  • User - Authentication: None
Authentication fields are hidden, but a user can modify activation names and descriptions
Delete Activation
  • Owner - Authentication: View or Full
  • User - Authentication: Full, View, or None
Can delete an activation

Run Activation

  • Owner - Authentication: View Export Results to Destination: None
  • User - Authentication: Full, View, or None

Users cannot run it if they cannot see it, so "Owner - Auth:View " is needed for UI.

Can trigger the run, but it will fail with a 403 error

Run Activation
  • Owner - Authentication: View or Full Export Results to Destination: Full

  • User - Authentication: Full, View or None

Can run it successfully