Most TAP Settings can only be created and modified by Organization Administrators.
There are several different user roles in TAP, and each has a different set of rights and privileges. When creating a user, select their role based on what features they need access to in order to do their job. Is a user tries to perform a task they do not have access to, a warning in the UI indicates they do not have permission to access that feature.
Important!
Users should already exist as a Triton User in the Triton User Management application before you create or use them in TAP. It is possible to add the user in TAP first and then add them in User Management, but TAP will show an error message ("Bad request: username not found") until the Triton User is created. As a best-practice, we suggest creating the Triton User first, which will then be verified by TAP when creating the TAP user.
User management functions are now performed in the Triton User Management application.
TAP user creation involves:
- Creating a Triton User in the Triton User Management application if they do not already exist there. (See: Triton User Management.)
- Applying content access control (CAC) restrictions to the user to limit their access to certain stations or podcast.
- Adding the Triton User (from Triton User Management) to TAP in the TAP User Management page.
- Assigning the user a role in TAP.
If the Triton User does not already exist in Triton User Management, you will see an error message ("Bad request: username not found"). If that happens, after creating the TAP user you should then go to Triton User Management and create the user there, with the exact same username. Ideally, you should create the Triton User first. Note that the user role that is defined in the Triton User Management is ignored for TAP.
TAP user roles are defined within TAP, not the Triton User Management application. However, any Content Access Control (CAC) settings you apply to the user in the User Management application are carried over into TAP. This means the user will only be able to create and access campaigns and flights for stations that the CAC settings allow. For more information, see Content Access Control and TAP.
Also note: the user status as displayed in TAP refers to their status within TAP. It doesn't necessarily correspond to the user's status in the User Management application. For more information, see Triton User Management.
User Roles in TAP
User Role Task Definitions
"Create" means the user can create the item; creating also includes managing.
"Delete" means the user can delete the item, as long as TAP allows the item to be deleted. (Some items can only be archived, because of rules around auditing, etc.)
"Manage" means the user can edit and configure the item but not create or delete it.
"View" means the user can see the item but cannot edit it (unless they also have "manage" permissions).
"Run" applies to reports; permission to run a report means the user can create and view the report.
“Mimic” means the user temporarily inhabits the role and permissions of another user. (See Mimic a User.)
Typical Roles Breakdown
The table below describes the various TAP user roles and what access privileges are enabled for those roles.
Role | Permissions |
|---|---|
Organization Administrator | Full creating, viewing, and editing permissions, including access to TAP Settings and creation/removal of targeting templates, as well as mimicking of other users in the organization. Organization Administrators should be assigned the "Advertising Super Administrator" role in the Triton Console. Organization administrators can see and edit all campaigns for all of the publisher's teams. |
Organization Programmatic Administrator | Can set user management permissions (create, modify, delete) for TAP Programmatic users. Only applies to TAP Programmatic; this admin user has no access to TAP Direct (the Ads tab in the TAP menu bar). Limited access to TAP Settings (Organization > User and Programmatic settings only). This role is used to provide organization admin privileges to users who only use TAP Programmatic. |
Account Executive | Permissions only apply to campaigns and flights where they are specified as the account executive. This includes:
|
Campaign Manager | Manage advertisers, campaigns, and flights, but not creatives. Create/remove targeting templates. The Campaign Manager can approve campaigns, and run reports, and can view but not modify TAP Settings. |
Trafficker | The trafficker is typically in charge of creating and scheduling flights and campaigns, and managing the traffic into the system and the lifespan of the campaign.
|
Read Only | Can view advertisers, campaigns, flights, and user lists, but cannot create, edit, or delete/archive them. |
Operative One API | Provides access to TAP advertisers, campaigns, and flights via the Operative One API. |
Programmatic Roles
TAP Programmatic replaces Yield-Op for programmatic advertising with Triton Digital.
Programmatic roles are used to enable access to the TAP Programmatic feature. The programmatic role is optional and independent from the user role. If your publisher has TAP Programmatic enabled, your users will need to have a programmatic role assigned. Otherwise they will not have access to the TAP Programmatic tab and its features.
Role | Permissions |
|---|---|
Publisher | Access to the TAP Programmatic tab and features. |
Also see: Best Practices when Adding Users.
Depending on your role, you might not have access to all of the tasks and procedures described in this user guide, or you might have limited access to tasks or procedures. Unless otherwise indicated, the descriptions in this user guide are from the point of view of an organization administrator with full access.