Understand organizations, teams, and users

Transcript

You know what’s really cool? With Fusion, you only need one login, and you only need to log in once to access all of the scenarios you’ll ever build. That’s right, you heard correctly. You only have to log in once, with how Fusion is organized from an administration level. In Fusion, you only have to worry about three org units: organizations, teams, and users. Each customer will have its own organization, and at this level, Workfront will calculate usage and billing. Consultants and partners will love that they can easily switch between organizations when working with customers, and not have to log in and out of different domains and systems. Teams are contained within an organization, and they are used to share and restrict scenarios, webhooks, keys, data stores, and we really want to stress, that connections are created and kept separate among teams, meaning I can’t create connection A in team A, and then use the same connection in team B, unless I go into Team B, and create that same connection. Customers will love that they can exclude scenarios, connections, and other vulnerable components from different teams within the same organization. Finally, users can belong to multiple organizations and teams. They, of course, will only have access to the organizations if invited, and it’s important to note that a user won’t be able to do anything in Fusion, unless they’re also added to a team. When creating users in Fusion, you’ll invite them at the organizational level first, giving them an organizational role of admin, member, or accountant. Then when adding to a team, you’ll give them a team role of team admin, member, monitoring, and operator. We’ll provide more details on how each role specifically behaves in documentation, but for now, if you’re the organization admin, you’ll have that role for orgs and teams. If you’re adding someone to work on scenarios, you can simply add them as members. -