Privacy is important, especially when sharing feedback or suggestions on a platform like Sleekplan. Sometimes, you might want to prevent users from seeing who left a specific comment or feedback post—while still allowing company admins to identify the author in the backend. If you’re using SSO , we’ve got a simple workaround to help you achieve just that.
How to Anonymize Usernames for Public Feedback
⛔The Issue: By default, Sleekplan uses the first part of the user’s email address as their public username. This can inadvertently reveal user identities to other participants on the feedback board.
✅The Solution: Instead of passing personally identifiable information to Sleekplan, you can configure your SSO (Single Sign-On) integration to send a random, non-identifiable username (or alias) in the SSO token. This way, when users leave comments or feedback, their true identity isn’t shown to others on the frontend—only a random name appears. The real user information still remains accessible to your team in the backend for follow-up and moderation.
👇Update SSO Token Generation
When generating your JWT token for SSO authentication, set the username field to a random string instead of the user's actual name or email.
Example: Let's say you have a user, “jessica.stone@company.com.” By default, others would see “jessica.stone” as the author of her feedback. With this workaround, her public username might now appear as something generic like “user_5834729” or a creative alias like “blue-otter,” while admins can still identify her as Jessica in the admin dashboard.
{
"id": "123456",
"username": "user_5834729", // <- Random/anonymous username for frontend
"name": "Alice Smith", // <- Real name, visible to admins only
"email": "alice.smith@company.com", // <- Real email, visible to admins only
}This is how the username would look like when displayed in the front end in the comment section of a feedback post :
With this simple adjustment to your SSO setup, you’ll give your team the privacy and confidence they need to share feedback honestly—while admins keep all the context they need on the backend.