Set a default company for all users | Community
Skip to main content
New Participant
December 22, 2023
Solved

Set a default company for all users

  • December 22, 2023
  • 1 reply
  • 1037 views

We only have one Company in our Workfront instance and I'm curious if there'd be any reason not to set that as the default for all users?  I know I can set a new SSO mapping attribute so the Company is set automatically, just unsure if there'd be any reason not to do that...?  Currently, the only users with the Company set are those with a paid license, all the reviewer license levels don't get the Company set.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by skyehansen

We occasionally get posts on this forum asking about splitting up one "company" into multiple companies, but the restrictive walls between companies usually leads to problems, such as a user who needs to report to two managers from two different "companies".

So everyone seems to recommend keeping a company as one "company", and therefore making it the default for SSO users doesn't pose any problems.

1 reply

skyehansen
skyehansenAccepted solution
New Participant
December 22, 2023

We occasionally get posts on this forum asking about splitting up one "company" into multiple companies, but the restrictive walls between companies usually leads to problems, such as a user who needs to report to two managers from two different "companies".

So everyone seems to recommend keeping a company as one "company", and therefore making it the default for SSO users doesn't pose any problems.

New Participant
December 22, 2023

Thanks!  That helps answer my question.  We have our SSO setup to align the users to the appropriate Group, but nothing at the Company level.

New Participant
December 28, 2023

For future troubleshooting purposes, the attribute mapping in the SSO panel is reapplied every time the user logs into Workfront. So if you ever do need to configure a user to a different company, that won't be a safe attribute mapping to use anymore if the user is also coming in via SSO. You'll update their profile, and the SSO login will revert it right back every time.

 

You may already know that one, but it cost me a frustrated hour or two of troubleshooting when we got started so I thought I'd share.