Logging in as another user, or assuming another user's identity

As an Admin, at times you may want to assume the identity of another user so you can view pages as if you were that user. This is now possible with Shotgun 6.3.10 and later.

Use cases

Assuming another user’s identity can be helpful in a number of ways:

  • To set up another user’s home page
  • To update settings for an individual user
  • To troubleshoot
  • To test permissions so you can see what an artist, coordinator, or anyone else, sees in your site and how their permissions work

How to assume an identity

  1. As an Admin, go to the Permissions page. Under the advanced tab, check the box that says “allow “sudo”: perform actions and log events as though logged in as another user *.”

  2. There are two ways to assume an identity.
    • Option 1: From any page, click the Design Page button and choose Use as Another User.



      A blue banner will appear at the top of the page. Use the search box to find the user or specific permission group you want to assume.

    • Option 2: From the People page, right click on a user and choose “Use Shotgun As...”

  3. Once you assume an identity, you will see:
    • a brief overlay acknowledging that you are now seeing the page as another user
    • a blue banner at the top of the page that tells you who you are logged in as.

    • Note: You are still logged in as an Admin, but you are using Shotgun as another user. This means you will be restricted to seeing only what that user has permission to see. For example, an Artist may only have access to one project.

  4. You can change the identity you are assuming at any time. If you would like to see the site through another user’s settings, then you can search for that user or a specific permission group in the blue banner.

  5. When you are ready to go back to Shotgun under your own identity, click “Exit” on the right of the blue banner.

Auditing Admin events

You can see the log history of the Admin assuming another user’s identity in the Meta Data field of the Event Log Entry for each project.

Note: The Who field shows the person whose identity the Admin was using, and the Meta Data field will show the actual user who generated the event.

Admin metadata

Follow

6 Comments

  • 0
    Avatar
    DJ Hauck

    This feature is great and long awaited, thanks!  Quick question, is there any auditing (log history) of "entering/exiting" this mode by the admin?  I assume all event logs would show up as the actual user you have assumed, so curious if we can know that the admin was operating under a sudo.

  • 0
    Avatar
    Brandon Foster

    Hi DJ,

    Glad you're digging the new feature! We'll update the doc with this info, but I can give you a quick answer now. Events generated while under the identity of another user will have some additional data in the Meta Data field for the event. You'll find a "sudo_actual_user" value detailing who the real person was that generated the event, rather than the attributed person on the Who field.

  • 0
    Avatar
    Juanmaria Garcia

    Really helpful feature!

  • 0
    Avatar
    Gary Chadwick

    Great feature! Using it already.

    Here's a slightly complex question. If I'm sudoed as one user, but have a separate Shotgun tab open will I then be acting as that user on the other page? Let's say I have a tab of a scene open. I use a different tab to sudo as an artist. If I then go to the scene tab and enter a note, is it recorded as me or them? I know that after refreshing the page will display the blue bar making it clear that I'm using their account, but does this take effect before I even refresh!

  • 0
    Avatar
    Brandon Foster

    Hi Gary,

    Any actions you perform in the first (scenes) tab after you have assumed another user's identity in the second tab will be attributed to the assumed identity user.

  • 0
    Avatar
    Kalvin Lyle

    Very useful!  This solves a lot of guessing and back and forth in troubleshooting with users.

Please sign in to leave a comment.