Create a connection - Basic instructions
Many Adobe Workfront Fusion connectors do not require custom configuration when creating a connection. This article describes the default connection creation process.
Access requirements
You must have the following access to use the functionality in this article:
table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header | |
---|---|
Adobe Workfront package | Any |
Adobe Workfront license |
New: Standard Or Current: Work or higher |
Adobe Workfront Fusion license** |
Current: No Workfront Fusion license requirement. Or Legacy: Any |
Product |
New:
Or Current: Your organization must purchase Adobe Workfront Fusion. |
For more detail about the information in this table, see Access requirements in documentation.
For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.
Create a connection
To create a connection inside a Workfront Fusion module:
-
Click Add next to the Connection box to open the Create a connection panel.
-
(Optional) Change the default Connection name.
-
In the Environment field, select whether this is a production or non-production environment. This information appears in the Connections area of Fusion.
-
In the Type field, select whether this is a service or personal account. This information appears in the Connections area of Fusion.
-
(Conditional) If the app requires advanced connection settings, such as an ID, key, or secret, enter that information.
You might need to click Show advanced settings to display the fields where you can enter this kind of information.
-
Click Continue.
-
In the sign-in window that displays, enter your credentials to log in to the app if you haven’t already done so.
-
(Conditional) If an Allow button displays, examine the actions that the connector will be able to take, then click the button to connect the app to Workfront Fusion.
note note NOTE Some Microsoft apps use the same connection, which is tied to individual user permissions. Therefore, when creating a connection, the permissions consent screen displays any permissions that were previously granted to this user’s connection, in addition to any new permissions needed for the current application. For example, if a user has “Read table” permissions granted via the Excel connector and then creates a connection in the Outlook connector to read emails, the permissions consent screen will show both the already granted “Read table” permission and the newly required “Write email” permission.