Adobe Workfront Fusion organizations and teams overview

Adobe Workfront Fusion’s Organization and Teams features make it possible for enterprises to control access to scenarios and other features within Fusion.

An organization is the largest entity in Adobe Workfront Fusion. For example, your Fusion organization may represent the Fusion account for your entire company.

Teams are smaller groups within the organization, and share Fusion resources such as scenarios, connections, and templates.

Organizations

Workfront Fusion users belong to an organization.

Users must be added to an organization before they are added to a team.

Organization roles

A user has one of the following roles in an organization:

  • Owner: The owner has all permissions available in the organization.
  • Admin: Admins can create and manage teams and users for the organization, and can approve templates.
  • Member: Members are able to use Workfront Fusion but are unable to make organizational changes.
  • Accountant: Accountants can see license information on the organization dashboard, but cannot perform any actions.
  • App Developer: Functionality for this role is currently unavailable, and will be made available in the near future. We do not recommend assigning users to this role at this time.

For information on specific actions available to users in each organization role, see Organization and team roles.

Teams

Teams are groups of users that share access to specific resources. These resources may include:

  • Scenarios
  • Connections
  • Webhooks
  • Keys
  • Data stores
  • Data structures
  • Email notification settings
NOTE
Because teams share resources, it is sometimes useful for a team to have only one member. For example, users in training may create connections to their individual Workfront accounts. Any team members would also be able to connect to the individual Workfront account. In this case we recommend that the user be the only member of a training team.

Organizations may have as many teams as they need, and users may belong to one or more teams.

Users can select their team from the dropdown list in the left navigation panel. Users only see teams that they are members of. Selecting a team will allow a user to access that team’s resources.

Team roles

A user has one of the following roles in each of their teams:

  • Team Admin: Admins can add, remove, or change the role of a team member. They can also perform any action available to the other team roles.
  • Team Member: The team member role allows users to create and execute scenarios.
  • Team Monitoring: The monitoring role allows users to access execution information for scenarios, but they are unable to design scenarios or change their “Active” status.
  • Team Operator: The operator role allows users to see execution data and change the “Active” status of scenarios.
  • Team Restricted Member: Functionality for this role is currently unavailable, and will be made available in the near future. We do not recommend assigning users to this role at this time.

For information on specific actions available to users in each team role, see Organization and team roles.

recommendation-more-help
7e1891ad-4d59-4355-88ab-a2e62ed7d1a3