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.
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.