Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

How are you using Company?

Avatar

Level 7
We've been having a lot of discussions internally about how we're using different aspects of Workfront. One of the things that we're looking at is our use of the Company field. Right now we use it as a flag to indicate the customer for each project. I know there are a lot of capabilities with Company around security and many other ways to use the field. I wanted to find out from everyone how they are using Company and the different use cases there are for the field. Thank you! Mohini Sinha, CSM Project Coordinator Excelsior College
0 Replies

Avatar

Level 2
Mohini, Until Groups and Sub-groups (and sub-sub-groups, lol) become more robust I still use Company as the top-level segregation component in an instance. For example, if you have an Enterprise with many brands or companies I would have them all as individual companies and then their divisions/departments would be groups under them. For cross-collaboration use groups and teams. Please keep in mind that this isn't a hard and fast rule and I suspect Group will continue to be elevated (per WF Roadmap) but until access can be restricted like you can with Company I find myself still deploying large organizations in this manner. If your Workfront instance is mostly operating within your department (ie not shared) then your use cases will most likely include external clients or vendors (as you mentioned) and potentially Legal or HR depending on your use and compliance requirements. I would NOT recommend using Company outside of those limited use cases, though, because from a Sys Admin and trouble-shooting standpoint it can be a challenge when someone says "why can't I see that update?". What are you thinking you may want to use Company for? John Albaugh

Avatar

Level 10
We're still implementing/deploying, but our plan was to use a Company for our inhouse agency, which leaves open other "Companies" being groupings of external users and to keep "vendor lists" (since Workfront can't do this sort of address-book functionality natively). Not sure if that is normal or not... Kevin Quosig

Avatar

Level 10
We have a global instance, with multiple Agencies/Business Units in it. So we use Company for two purposes: 1) for client work, its the Client Name (and is populated via an integration with SAP) 2) for internal work and for our user profiles, its the Agency name We use Groups to segregate our individual agencies. Katherine Haven, PMP VP, Director, Business Technologies - PMO FCB

Avatar

Level 6
Same as Katherine, we use it for our clients (only real downside is, that on the company view you are not able to see all the projects related to that company) and to seperate our entities. Chris c.budgen@emakina.at Emakina CEE

Avatar

Level 4
We use Companies for our clients that have different billing rates. We attach the roles and their specific billing rates to that Company. This way, when Project Managers create projects they add the Company to their project. Thus, overriding the system "Role" billing rates and use the Company billing rates. Leslie Tanner CreativeDrive

Avatar

Level 3
I'd be interested to know more about your SAP integration. Are you doing this via API or Fusion? What elements are you moving to/from SAP? Jim Brown FujiFilm Medical Systems, USA