Permission name to see studio and admin
I created a custom user dropdown, and I would like to display the Studio and Admin page links in this dropdown based on permission. I do not want them to be attached to user rank or role in case we c...
Forum Discussion
You have to be an Admin on Stage in order to see Studio, and you can only get to it via Stage.
I strongly recommend that you create a role for this type of permission, though, so that you're not managing permissions at the user level. It gets tricky and it's also hard to track. You can add the role at the community level and when you want to change who can access it, you just remove the role from their profile. And it's much easier to manage groups of people this way, too.
lolagoetz but even if I created a role that is like "can use studio" and a role that is "can use admin" - what permission do I give them for that role? Like what is the permission for "can view admin" and the permission for "can view studio"?
These permissions are not individually broken out, but are all tied to the Administrator role on stage.
Are you using your stage for user acceptance testing and you want to share studio access with designers? Can you share a bit on why you want to offer these links to someone outside of the stage admin group?
Claudius lolagoetz We want certain users, like people from our Marketing team, to see the Studio link so they can edit our email templates, but not be granted full administrator privileges.
On our second stage server that we used as a test for something, we had users that were granted roles other than administrator, and they could see the Studio link in the "Category dashboard" OOTB component, but it was not showing up in the custom dropdown of user links that I created. This is what I am checking for whether or not I should be displaying that Studio link:<#if user.ranking.id == 1>What is category dashboard using to display the Studio link to those users that had permission to view Studio without being an administrator that I can use in my custom dropdown instead of the above code snippet?
You could potentially give them a "Studio" role (or whatever you want to call it) on your stage server, and update the appropriate permissions in these sections:
Are you allowing them to push from Studio, or only make updates?
If you want them to have rights to push, you'll also need to update these in prod:
I will say up front that I've not tried to decouple these permissions and create a role that only does a portion of these and not all.
But this is where you'd do it.
