Grant Adobe I/O integrations access to workspaces and assign roles
- Topics:
- Administration & Configuration
CREATED FOR:
- Admin
Enterprise Permissions allows Target customers to use a single organization, but divide it into workspaces for their different teams or workflows.
The Enterprise Permissions feature facilitates effective scaling of optimization programs across teams. Although the feature was available in the Target UI, the Admin APIs lacked the corresponding support until earlier in 2019. In the Target February 2019 release, Adobe updated the Admin APIs so that you can use the integration account to access all workspaces created in your organization. So, while earlier, Admin APIs were restricted to just the default workspace, the February 2019 update granted access to all workspaces with Approver access.
With the Target September 2019 release, Target Enterprise Permissions provides customers with the following access controls:
- You can choose the workspaces to which the integration can be applied
- You can apply a role to the Adobe I/O integration: Approver, Editor, or Observer.
This update supports the following use cases:
- Grant the Adobe I/O integration access to all workspaces with the Observer role for reporting purposes with no rights to create or edit resources.
- Grant the Adobe I/O integration the access to select workspaces with the appropriate role to allow a central team to make API-driven changes in only a few workspaces.
- Allow each team owning its workspace to have its own integration whenever the team is ready to explore APIs and choose the role accordingly.
- Mix and match any of above scenarios.
Action Needed: Those customers who are currently leveraging APIs for CRUD operations on resources (activities, audiences, offers, and reporting) across all workspaces need to grant their existing Adobe I/O integration access to all workspaces with the desired role as per their use case. You can do so by selecting each Target Product Profile in the Adobe Admin Console and adding the integration(s) in the Integration tab. Prior to the September release, all integrations operated using Approver access, regardless of choice made from the Product Role drop-down list. You can now choose the desired role.
To grant Adobe I/O integrations access to workspaces and to assign roles:
-
Open the Adobe Admin Console.
-
Click the Products tab, then select the name of the desired product.
-
Select the desired workspace (Product Profile).
-
Click the Integrations tab.
-
(Conditional) To add a new integration, click Add Integration, select the desired integration, then click Save.
-
From the Product Role drop-down list, select the desired role for that workspace:
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.
Target
- Adobe Target Business Practitioner Guide Home
- Target release notes
- Introduction
- Introduction to Target
- Access Target from the Adobe Experience Cloud
- Target key concepts
- Understand the Target UI
- Adobe Target welcome kit
- Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Target at a glance
- Chapter 3: Develop your testing and personalization ideas
- Chapter 4: Tips for using Target
- Chapter 5: Inspiration for testing and personalization activities
- Chapter 6: Easily avoidable pitfalls
- Chapter 7: Create and run your first Target activity
- Chapter 8: Communicate your activity results
- Chapter 9: Next steps and resources
- Glossary
- How Target works
- Training and certification
- Training videos for Target Standard and Premium
- Target optimization and personalization FAQ
- Administer Target
- Implement Target
- Integrate Target with the Experience Cloud
- Adobe Analytics as the reporting source for Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- A4T support for Auto-Allocate and Auto-Target activities
- Use an Analytics tracking server
- A4T reporting
- Troubleshooting the Analytics and Target integration (A4T)
- A4T Frequently Asked Questions
- Expected data variances between Target and Analytics when using and not using A4T
- Integrate Target with Adobe Customer Journey Analytics
- Integrate Target with Adobe Journey Optimizer (AJO)
- Experience Cloud Audiences
- Integrate Target with Adobe Experience Manager (AEM)
- Integrate Target with Adobe Audience Manager (AAM)
- Integrate with Real-time Customer Data Platform
- Integrate Target with Adobe Campaign
- Adobe Analytics as the reporting source for Target (A4T)
- Activities
- Activities overview
- Target activity types
- A/B Test
- Auto-Allocate
- Auto-Target
- Automated Personalization
- Automated Personalization overview
- Random Forest Algorithm
- Create an Automated Personalization activity
- Upload data for the Target personalization algorithms
- Data collection for the Target personalization algorithms
- Estimate the traffic required for success
- Preview experiences for an Automated Personalization test
- Target Automated Personalization offers
- Manage exclusions
- Offer reporting groups in Automated Personalization
- Select the control for your Automated Personalization or Auto-Target activity
- Automated Personalization FAQ
- Troubleshoot Automated Personalization
- Experience Targeting
- Multivariate Test
- Recommendations activity
- Edit an activity or save as draft
- Priority
- Activity settings
- Success metrics
- Activity change log
- Troubleshoot activities
- Activity QA
- Audiences
- Experiences and offers
- Experiences and offers overview
- Visual Experience Composer (VEC)
- Visual Experience Composer overview
- Visual Experience Composer options
- Visual Experience Composer changes
- Include the same experience on similar pages
- Multipage activity
- Activity collisions
- Modifications
- Element selectors used in the Visual Experience Composer
- Mobile viewports for responsive experiences
- Visual Experience Composer best practices and limitations
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Visual Experience Composer overview
- Troubleshooting the Visual Experience Composer and Enhanced Experience Composer
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Enhanced Experience Composer
- Enabling mixed content in your browser
- Page modification scenarios
- Visual Editing Helper extension
- Visual Experience Composer helper extension
- Redirect to a URL
- Creating carousels that work in the Visual Experience Composer
- Form-Based Experience Composer
- Single Page App (SPA) Visual Experience Composer
- Offers
- Reports
- Recommendations
- Recommendations overview
- Introduction to Recommendations
- Plan and implement Recommendations
- Entities
- Criteria
- Criteria overview
- Create criteria
- Create criteria sequences
- Base the recommendation on a recommendation key
- The science behind Target’s recommendations algorithms
- Upload custom criteria
- Dynamic and static inclusion rules
- Use a backup recommendation
- Work with multi-value attributes
- Use Adobe Analytics with Recommendations
- Design
- Activity
- Recommendations as an offer
- Frequently asked questions
- Recommendations Classic documentation
- Troubleshoot Target
- Target APIs
- Resources and contact information
Adobe Target Maturity Webinar Series
Adobe Customer Success Webinars
Tuesday, Feb 4, 4:00 PM UTC
Adobe Target innovations, including GenAI, and best practices on AI-powered personalization and experimentation at scale.
Register