This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Sometimes, I need to investigate others' workflows and therefore, I put myself in their private studios...but when I do that, my workflow schedules become disabled since those were created by me in my own private studio.
Hi @JohnBell, what I have done (and my fellow Curator did this as well) was to create multiple users for yourself. You need to have a typical user set up with your own studio and you can keep all of your work there, especially the scheduled stuff so it doesn't break. Then, create dummy accounts for yourself that are associated with the other studios. That way you can log into the dummies to keep an eye on other studios without breaking your own. Gallery users are free to create, so while not an ideal set up perhaps, it really only takes 10 minutes to set things up that way then you can move freely between studios with confidence.
For myself, I just create a fake email address that's easy to remember. For instance if my real work email is mcurtis@whatever dot com, I'll create a user based on the email mcurtis2@whatever. We have different studios for each department, so I've actually created accounts like mcurtisFinance@whatever and mcurtisOps@whatever, that way it's easy to remember the fake email names. You set your own password when creating the account, but make sure to remember it since the whole reset my password thing won't work (can't go into your fake email to get the reset pass email). Now you can have 3 or 4 different accounts, each aligned with the different studios, and you can hop between them without your schedules disabling.
Whether you can create new users will depend on the type of authentication you use on your Gallery. I assume you use Windows AD to authenticate which means that the new users will need to exist in the AD and you will need to sign in using the user credentials for the user to be created on the server side.