Employee Access & Permissions

I think custom user roles are most helpful for this kind of thing. Helps segment your users and you can decide exactly which parts you want them to have access to.

+1 to what @daniel.truman suggested. 

On top of custom roles, we provide admin access to a few members of our wider team. We look at a couple of variables, like what type of tasks they need to accomplish, how often they would need access, how many licenses we have, etc.

When working on our community content calendar, we have employees submit requests through Airtable. With Zapier and Slack, the community team is then alerted to new content requests. The community team can then make use of the Gainsight CS admin license, and schedule, change authors, etc.

For casual posts, like replying to a customer’s question or a product enhancement request, employees are encouraged to do that from the front-end. They don’t need to check in with us but we do have a custom role for employees, along with the tag and icon.

@security_lion thank you! this is kind of what I was wondering if anyone else has done. I’d like to give admin access to a few members on the team. I think I am going to need to evaluate this on another level. Thanks again. 🤗

Glad it helped,  @baraica 🙂

Two other points that came to mind,

Including a quarterly check on your team (admins). You can see when users last logged in or where active, so if you find that a product manager or PMM hasn’t been active in 4 months, it might be a good signal that they don’t really need to be admins (or maybe they left the company and you weren’t alerted 😮).

We also have an internal enablement guide that is required for any moderator, community manager, or admin. I’ve had 2-3 employees go through it to realize they didn’t know what they were asking for and end up backing out of needing the license.

Good luck setting up your system! 

@baraica you could also create a workflow where your Product Marketing team send you the content they would like to post and then your community team can create the Article or Product Update whilst posting on behalf of a community member from Product. Simply change the Author when creating these topics:

I have not used Gainsights product long enough to fully know if this is capable yet. I am looking into this or something similar as we roll out Gainsight however!

At prior organizations we had custom roles added to individuals who contributed content. These individuals would get an “Author”, “Editor” and “Publisher” role. These are just as you’d assume. The ability to create, edit or publish the content on a specific page. Managers / Approvers would get the publishing capabilities while contributors would obtain the Author or Editor based on their position. (they could get both of course) 

This gave our organization the ability to create a process approval workflow for all content. Admins / community team could help incase of an outage/vacation of “Publisher”.

Best of luck whichever way you choose!! 

Hi! What you described is exactly what we’re looking for. The ability to publish and edit articles but without granting admin rights. Is this possible with a custom role in GS CC? From what I’ve checked the settings on custom roles are related to access in control only. Grateful for any tips!

From what I have experienced so far, there is not a way to do this. Someone would have to have the “Moderator” role. This would allow them access to do all three tasks. There is not a way to restrict, from what I can tell, on publishing. 

I was thinking about this. You could also create a custom role to only allow specific people to post new items inside of a location. This would not require people to receive full moderator role. This would restrict the people who can post and you can control replies separately. 

thank you, ​@mitchell.gordon. It it something we can do ourselves or would it be a customization? I was thinking of exactly that solution since we had this in Khoros, but creating custom roles here seems to be much more simple. Or I just haven’t found the correct place yet :)