Step 2: Give the Technical Account Access

Choose what the technical account can reach in Workfront Fusion, and grant that access.

Overview

Where this fits: 1. Create credentials → 2. Give the technical account access → 3. Call the API or use the Adobe Fusion connector

When you create an OAuth Server-to-Server credential, a technical account is added to your Fusion organization as an organization member on no team. By default it can't see anything. Requests authenticate, but they return little or no data.

Choose an access level

Option 1: Team access
Option 2: Organization-wide access
Use when
The integration only needs specific teams
The integration must reach every team, for example a control center that lists or exports all scenarios
Reaches
Scenarios and data in the teams you add it to
Scenarios and data across the whole organization
Fusion role
Team member
Organization Owner
Admin access in the Adobe Admin Console
Not required. Add it only for admin-level actions
Required
Principle
Least privilege
Broad access, simpler to manage

Admin-level actions, such as viewing and exporting activity logs, always need admin access in the Adobe Admin Console. Option 2 already includes it. With Option 1, add it as an optional extra step.

data-variant=info

data-slots=text
Admin access on its own doesn't give access to scenarios or data. The technical account must also be a team member (Option 1) or an Organization Owner (Option 2).

Before you begin

The technical account email is shown on the project's Credential details tab in the Adobe Developer Console. For example, 19647e9d-4209-4770-9550-834d1d52ed7d@techacct.adobe.com:

Technical Account Email on the Developer Console credential page

Fusion creates the matching user automatically. It's listed in Org overview > Users with the role Member and the status No Teams:

The same technical account user inside Fusion

Option 1: Team access

Use this option when the integration only needs specific teams. No admin access is required.

Add the technical account to teams

  1. In Fusion, open the Teams tab and select the target team.
  2. Add the technical account user with the right team permissions.
  3. Repeat for each team whose scenarios the integration must reach.

Optional: Allow admin-level actions

If the integration also needs admin-level actions, such as viewing and exporting activity logs, make the technical account an admin in the Adobe Admin Console. Follow Grant admin access in the Adobe Admin Console. You don't need to change its Fusion role.

Option 2: Organization-wide access

Use this option when the integration must reach every team. It takes two steps, in order: first make the technical account an admin, then give it the Organization Owner role. Only admins can be given the Organization Owner role. This option also covers admin-level actions such as activity logs.

1. Grant admin access in the Adobe Admin Console

  1. Go to adminconsole.adobe.com and open the Products tab.
  2. Select Workfront Fusion. Open the correct organization instance and its product profile. If you're prompted, choose your Production instance.
  3. Select the Admins tab and click Add admin.
  4. Enter the Technical Account Email and click Save.

The technical account now appears as an admin with the ID type Technical account.

Admin Console, Workfront Fusion product, Admins tab listing technical accounts 

data-variant=info

data-slots=text
The technical account doesn't appear in the product's Users list, even though it exists in Fusion. Add it directly from the Admins tab.

For more details, see Add users to Adobe Workfront Fusion through the Adobe Admin Console.

2. Make it an Organization Owner

  1. In Fusion, open Org overview, then the Users tab.
  2. Find the technical account by its @techacct.adobe.com address. It shows as Member with No Teams.
  3. Set its Role to Owner.

Fusion Org overview, Users tab. A new technical account shows as Member with No Teams

Next step

The technical account is ready. Choose how you want to use it: