Best Practices for Setting Up Groups in Fusion

[Kellie_sphere]

I'm looking for Fusion best practices for setting up organizations where multiple groups will utilizing the system in tandem for their group processes.

Examples on:

• How to set up Teams
• What access levels to give
• Once teams and access levels are setup, how to control that users are only using the "service" accounts and not establishing personal connections to platforms.

[monicacardoso]

Hi @Kellie_sphere, 

Thank you for your question! Our documentation HERE explains how to setup teams in Fusion. There are no access levels in Fusion, but you must select a Role for each user. I would recommend making one user a Team Admin and all others Team Members. 

As far as controlling their accounts, this is challenging because Fusion currently does not have a built-in way to restrict who can create connections at a platform level. Fusion allows you to setup connections to different services using the available modules.

For example, a user can setup a connection to their Workfront account using a Workfront module. They could technically login using their personal credentials and not a Service account. If you wanted to restrict that, you could ensure that their access level in Workfront does not give them System Admin permissions. That way, if they tried to perform an action in Fusion that required System Admin permissions, they would run into an error message. 

HERE is a list of all apps and their modules.

- Monica

[kautuk_sahni]

@Kellie_sphere Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!