Configuring kudos for your organization
This article shows org admins how to turn kudos on or off, choose where posts land, define categories and values, and allow or block anonymous recognition.
Before you begin
- You need org admin permissions in Dailybot.
- Decide which chat channel (or channels) should receive kudos posts for each connected platform.
Steps
- Sign in to Dailybot and open Settings > Organization (or Kudos under org settings, depending on layout).
- Locate Kudos and toggle Enable kudos on for the org, or off if you need to pause the program during policy review.
- Set the default destination channel (Slack, Microsoft Teams, Discord, or Google Chat) where public kudos should appear unless a sender picks another allowed channel.
- Open Categories or Values and add the labels you want senders to pick from (for example, “Teamwork”, “Customer impact”); remove unused labels to keep the list short.
- If your plan supports custom points or weighting, assign values per category only when it helps reporting; otherwise keep categories descriptive only.
- Find Anonymous kudos and choose Allowed if people may send without showing their name, or Disabled if every kudos must attribute the sender in admin logs and posts.
- Save changes and post a test kudos from a non-admin account to confirm routing, categories, and anonymity behave as expected.
Who can send and receive kudos
You do not maintain a separate “kudos recipient list” in most setups.
To let someone receive kudos: they must be a member of your Dailybot organization and connected on your chat platform (Slack, Teams, Discord, or Google Chat). When a teammate sends kudos, they pick the recipient from the people Dailybot knows in that workspace.
If someone is missing from the picker:
- Confirm they joined the org under Organization > Members — see Managing members.
- Confirm they completed onboarding in chat (the bot can see their account).
- Confirm kudos is enabled for the org (step 2 above).
- Ask them to send or receive a test kudos from the web app or chat command — see How to give and receive kudos.
Guests or contractors only appear if your plan and chat integration expose them to Dailybot the same way as full members. If your IT policy limits guest accounts, those users may be unable to send or receive kudos until they are full workspace members.
Settings reference
| Setting | Effect |
|---|---|
| Enable / disable | Org-wide on/off for sending new kudos |
| Destination channel | Primary place Dailybot posts public kudos |
| Categories | Structured tags senders select or admins report on |
| Anonymous | Hides sender in the public post when allowed |
What to expect after
Members see the updated category list and channel behavior immediately after save. Historical kudos keep their original metadata.