Skip to main content
Tutorial

How to mark a colleague as retired employee on the community

  • December 13, 2018
  • 5 replies
  • 389 views

Julian
Forum|alt.badge.img+5
  • Gainsight Employee ⭐️⭐️⭐️
  • 908 replies

When a colleague has left the company, you also want to make sure that other users on the community are aware of that. Otherwise they might expect a reply to a private message, or a response after mentioning them in a thread.

There are two things you need to do when a colleague does not work on the community any more:

  1. Make sure that this user is not able to use this account
  2. Update the profile so that other users notice that he/she has retired

To make sure that the user is not able to log in and use the account in the future, you should ban the user or change the login details (so change the password or the SSO ID, depending on which login you use). Both options can be found in the profile page in the Control environment.

To update the profile of this user, you should assign this user a rank that has the addition "retired" in it. This is how a retired Moderator should be displayed:
 

3d9944f7-624b-42e0-a29c-5056d30d7019.png


How to do this

First, you will need to create a Custom user role ([Settings] - [User Roles]) so that you can assign that role to a user that is retired:

 

 

e24eeb79-bc0d-4f43-a7b4-bcc4fadfc5d4.png


Once you have created such a custom user role, you need to assign this to the user:

 

 

 

 

97b3775a-cfa6-492f-a046-7ee299bb41aa.png


Then, as a last step, you need to create a rank with the name that should be displayed (here "Retired Moderator") which can only be received when a user has this custom user role:

 

 

 

 

07638094-4c09-440e-a91e-107c89f77226.png


Note: As this rank is achieved by a custom user role and not by user activity, please add 0 for all values that are required for this rank (e.g. 0 posts, 0 topics, etc.).

After you have saved this, the users that have been marked as retired will automatically receive this special rank.

 

 

Did you find this topic helpful?

5 replies

emiller
  • Contributor ⭐️⭐️⭐️
  • 16 replies
  • September 24, 2024

@Julian Is this guide still current? I tried following these steps, but was unable to create a rank with 0 for the number of interactions fields (posts, comments, likes, etc).  I got the following error when I tried to save the new rank because it appears that 0s are not acceptable as values for any of the fields?

 


emiller
  • Contributor ⭐️⭐️⭐️
  • 16 replies
  • September 24, 2024

Second screen shot showing that I tried to configure it to use the role instead of the stats:
 

 


Julian
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • 908 replies
  • September 25, 2024

Thanks for flagging this. I just tested it and it worked for me without any issues. So I am also a bit confused why you are receiving this message… Hopefully it was just a temporary issue and it works for you as well now. 

Sometimes I forgot to fill in an individual field, which would cause the system to not accept it - but the number of error messages hints that something else was going wrong. Should the issue persist, please reach out to the support team, they should be able to investigate this properly.


emiller
  • Contributor ⭐️⭐️⭐️
  • 16 replies
  • September 25, 2024

Hi @Julian and thanks for the reply. I tried it again and got the same result. I decided to randomly try changing something. Originally the external name for the role was "Former Moderator" and the internal name was “Former Moderator (Inactive).” when I changed the internal name to match the external name exactly, I was able to create the rank. It looks like the error is thrown when either the rank names don't match exactly or when punctuation is used, such as the parentheses. Seems like that might be a bug?  I did log a case.


Julian
Forum|alt.badge.img+5
  • Author
  • Gainsight Employee ⭐️⭐️⭐️
  • 908 replies
  • September 26, 2024

Thanks for getting back to me on this - I tried it again with the names that you mentioned, and everytime it just worked like a charm… Good that you have logged a case, because to me it sounds like an individual bug in your community instance.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings