Connection overview

Workfront Fusion requires a connection for most applications. It uses this connection to communicate with the given third-party service.

For example, if you want to create a scenario that retrieves information from Workfront, you must grant permission for Workfront Fusion to access your Workfront account.

A connection represents the authorization and permissions that Fusion uses to access the application. You can create one or more connections for each application used in your scenarios, and can use the same connection in multiple modules or scenarios.

Most connections are used only for a single application. For example, a Workfront connection cannot be used in a Salesforce module. Some Adobe applications can share connections. For details, see the articles for those applications, listed in Fusion applications and their modules references: article index.

Connections are owned by teams. All members of a team have access to the team’s connections, and users outside of a team do not have access to the team’s connections.

Access rights

For every connection, Workfront Fusion requires only those access rights that are necessary to successfully complete a given scenario. For example, if you create a scenario to download a document from Workfront, Workfront Fusion does not ask for permission to create a new project. Later, if you find that you need to create a project, you can update the connection or create a new one that can create projects.

Not all services allow you to limit access to specific tasks. In these cases, Workfront Fusion must require full access rights. For more information on how to restrict Workfront Fusion access to your account registered to those services, see the application-specific documentation listed in Fusion applications and their modules references: article index.