Companies and Groups Setting Up

[ThomasNe2]

Hi folks - I am looking for advice/suggestions more than anything in about the best practice for splitting up my Workfront instance.

We are expanding and onboarding other brands and business units from within our organisation. Our Groups and Companies set up is currently quite duplicative and I am wondering how best to utilise them so we can separate areas of the system. We will have certain areas that need to be restricted to the brands/business units that will utilise them and other areas that all users will need access to. 

Just wondering if anyone has any best practice or suggestions on how they have done this successfully?

Thanks in advance!

[Srinija_N]

• Periodically evaluate your existing Workfront organizational structure to ensure it meets your needs.

• Only one company is typically needed for your internal users.

• Create companies for external clients or vendors that you want to track in your Workfront instance or who need login rights to your instance.

• Keep Workfront groups to a minimum and correlate them to your organization’s departments.

• Use groups to represent the department structure and teams to represent the working structure.

• Leverage group administrators to help system administrators manage users and settings.

• Allow group administrators to create their own subgroups.

• Use larger organizational units to share items with sets of people.

You can find more details on these best practices in the experience league

https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/best-practices/organi...

Following these will help you to maintain easier and a sustainable product. Have Fun!

Thanks!

[Lyndsy-Denk]

In our instance almost everyone belongs to a single company. We use portfolios that are assigned to certain groups to isolate work. The group that is assigned to the portfolio manages the programs within, however other groups and teams may own projects in those programs to support reporting on cross-functional initiatives like a product launch.

Where I find companies useful is to isolate further, especially for the sake of information security. I have two examples:

1. We have one group in our system that never will work with our primary users, so I've considered giving them a dedicated company.
2. Third-party users like creative vendors. Assigning those users to a company gives me, as the admin, stronger control over what they can see in the system. In general, they can now only participate in things that have been shared with them directly. You can limit their visibility to see communications from the primary company or with other companies.

[kautuk_sahni]

@ThomasNe2 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 really benefit the community. Thanks again for being part of the conversation!