Kudos visibility and privacy settings
This article shows org admins how public versus private kudos behave, how channel visibility works, what dashboard-only mode does, and who sees each layer.
Before you begin
- You need org admin access.
- Decide whether recognition should default to a wide channel or stay inside Dailybot for regulated teams.
Steps
- Open Settings > Organization > Kudos (or the equivalent Recognition panel).
- Set the default visibility to Public if posts should go to the configured chat channel, or Private if only participants and admins should see the entry in Dailybot.
- Under Channels, allowlist the channels where public kudos may post; remove channels that should never receive recognition noise.
- Enable Dashboard-only (sometimes labeled Web only) if kudos should appear in the Dailybot app and leaderboard but not mirror to chat — useful when chat logs are exported broadly.
- Review Anonymous kudos: when allowed, the chat post hides the sender name but org admins still see sender identity in moderation tools for abuse investigation.
- Save settings and send a test kudos from a member account to verify each combination: public channel, private, and dashboard-only.
Who sees what
| Mode | Members in chat | Members in web | Admins |
|---|---|---|---|
| Public + channel | Yes, in allowed channels | Yes | Yes + audit |
| Private | No broadcast | Involved users + admins | Yes + audit |
| Dashboard-only | No chat post | Yes | Yes + audit |
| Anonymous public | Sees text, not sender in channel | Per your UI rules | Sender visible for moderation |
Exact labels in the product may differ; map your screen to the behaviors above when training the team.
What to expect after
Senders only see options your policy allows, so fewer mistakes hit the wrong channel. Compliance reviews can rely on dashboard history even when chat stays quiet.