Admin Console

​@skyehansen ​@Gokul_Agiwal ​@anupampat  Wanted to loop you in and see if you have any perspective or lessons learned that could help us here. Your insight would be helpful, thank you!

I think it’s not unusual for the Admin Console product to be managed by a different team -- for example, marketing ops might own or manage the workfront product while IT or security teams might manage the admin console product. This is especially true of the larger enterprises. If this describes your situation, I would suggest you work it out with your infosec or IT teams in terms of who and how they would allow to connect (rules, policies, etc.). Even if you’re running your own Admin Console, I still would advise you coordinate with IT/infosec as a CYA step, as it would be strange for IT to NOT have a policy about it (you’d want to get that in writing!).

In terms of adding non federated IDs or IDs federated elsewhere it hasn’t been a problem from the admin side (it’s fairly simple to manually add a new user and I’ve also worked for a number of companies that have at least added Adobe consultants.). From the user side, they might experience a slightly different login experience -- you could set up a screenshare with one and record it in order to provide training for other future users of the same type.

I’ve come across the an issue working with a couple of external companies that have consoles set up. If their users are already federated, then it’s an easy process, but if they have Domain Enforcement turned up, this stops other organisations from creating Adobe ID in their console with domains that are “owned”.

The solution, is to get the other organisation to add the user the user to their console as federated, then you can add them to yours without issue.

This extra step can lead to longer turn-around times to complete the request, so the process needs to be managed and communicated to stakeholders.

I don’t know if this is the same, but sounds similar to the horrible time we’ve with external users for proofing and the admin console. Very long story but we add the email address to proofs, it makes them sign up, but they aren’t always getting into the console giving errors. Lots of proofing time lost and a horrible experience for our external users.