Configuration Guide

@Kudozza is a Microsoft Teams application which focuses on increasing appreciation within an organization with the help of kudos. All with the goal of strengthening the team culture.
While it works out of the box (once installed to a team), it has some tools and settings which benefit from being tailored towards your organization’s setup.

Prerequisit: Installation

There is a dedicated installation guide which describes how Kudozza can be installed to a team.
It covers topics which are also important for the governance:

  • Installation in teams.
    We recommend to rollout Kudozza to all teams of an organization so it is omnipresent to the users
  • Adding the Kudozza tab to channels.
    At least every General channel of a Team should have a Kudozza team tab configured as it contains team related information
  • Configuration of Kudozza administrators.
    Only the users who installed Kudozza to a team are automatically made Kudozza administrators. You might want to promote additional colleagues to Kudozza administrator.

Once these basic steps are done, there are further configurations that can be done:

Kudos Notifications&Overview

Kudozza follows the principle that praise is most powerful if it is shared in public.

Kudozza has two different mechanisms that increase the visibility of kudos to a wider audience:

  • Arena channels
  • Kudos Digest

The Kudos Digest view is part of the Kudozza Team Tab and also available in the personal mode of Kudozza. The difference is that in the teams tab, only kudos of the specific team are displayed while in personal mode kudos of all the teams the user is a member of are displayed.

Kudos Digest views have the downside, that they require the user to visit the page proactively to view all the kudos.

To get notifications whenever a kudos is posted, you can set up a dedicated channel per team with the naming convention Kudozza Arena or Kudos Arena. Kudozza will then automatically send a notification for each kudos given in that team into that channel. Users just need to follow that channel and will get notifications for each kudos.
It is also possible to have an organization wide Kudozza Arena channel. If you would like to have that configured, please contact us (Kudozza currently lacks the self-service configuration for this).

User ranking

Within the Kudozza Team Tab there is a user overview.

User overview in Team Tab

By default, it displays the statistics of the current user, a banner with the active challenges and information about all other team members who have used Kudozza in the previous time period in this team.
Depending on your organization regulations and member sensitivities, you can restrict which information is displayed here about the other users.

Kudozza allows for a fine grained control of what is displayed within the personal mode->Administration->Privacy. The options are:

  • Show no information about the other users at all. Only information about the current user.
  • Show only the participants in a currently active challenge. Without kudos or score or ranking.
  • Show all users with the number of given and received kudos but without score and ranking.
  • Show only the top 10 users with score and ranking. This is to motivate users by showing what is possible to reach.
  • Show all users with score and ranking (default).


Users can use #hashtags in kudos by simply typing the # sign in the text entry dialog.
A list of pre-configured hashtags is displayed to choose from. However, the user can also freely enter whatever hashtag is on his mind.

The pre-defined list can be edited within personal mode->Administration->Categories (category is the Kudozza wording for hashtag).
Feel free to delete the Kudozza defined categories and add new ones.

Categories with images

Categories can have an image associated. This is useful if you want to emphasize a category/hashtag.
A common use case are company values: A kudos tagged with a category/hashtag representing a company value can be highlighted this way.
But it is also fun to just add some seasonal decoration to kudos (e.g. introduce a #xmas hashtag that displays some xmas decoration in the kudos when used)

A sample with a category image

To add an image to a category, use the edit button on an existing category.
You can add more than one image to a category. Kudozza will then pick randomly on every kudos.
Psychological research shows that users are more likely to perform an action if the outcome has a surprise element. In this case, the random category image.

Emoji - Icons

Users can leave an emoji reaction to every kudos. By default, a user can pick only from the standard set of emojis.
Kudos reaction

In the paid plans, it is possible to upload department/team logos or logos for technical stacks or products.
Experience shows that users love to add these custom reactions and often use them to give a kudos more meaning or team identification.
Also not so serious usages are common where the upload is used for the most recent fun icons.
A good source for this sort of icons is the Slackmoji website. If you find some you like, you can add them via the emoji upload to Kudozza.

Although every user can upload emoji reactions, you might want to set the stage by already uploading some initial icons. The functionality is located at personal mode->Custom Emojis.

Insights - Statistics

Kudozza has two types of statistics:

  • Team specific statistics within the Kudozza Team Tab are accessible to all team members
  • Global statisistics within personal mode->Administration->Insights page. Accessible only to the administrators.

The global statistic reports across all installed teams and give you a good idea how Kudozza is used across the organization and in which teams most kudos are given.

Within that statistics, there are parts that cover user specific data. We know that this is difficult for a lot of companies. Therefore, we have the possibility to remove the user statistics from the Insights page.
If you want the user data removed, please let us know through the contact form.


The goal of a “kudos culture” is that the giving of kudos becomes a habit within your organization: “I see something good and noteworthy = I give a kudos”
To form a habit it is necessary that users give kudos frequently.

Kudozza provides here an incentive through badges which are given for frequent usage.
Kudozza has some default badges based on the points a user gets by giving, receiving or taking part in a kudos.
The points and the badges are visible in the Kudozza Team Tab. Whenever the user reaches a given number of points within a period (75days) he is permanently awarded a badge.
Exemplary badge:

Example of a point badge


The idea behind a challenge is to ask users to commit into the giving kudos for a longer period. This has multiple effects:

  • The users can develop a habit of giving kudos
  • If many users take part, the benefits of a kudos rich culture become obvious

Challenges can be scheduled on the page personal tab->Administration->Badges&Challenges.
Challenges are organization wide, people across all teams can join them.

A challenge can last a freely defined number of weeks. A challenge week always starts Monday UTC at 00:00 and ends Sunday UTC at 23:59.

Users can onboard into a challenge in its first week by giving the number of kudos defined in the challenge.
Prepare the users before a challenge starts so they do not accidentally miss the first week.

Users taking part in a challenge are visible in the Kudozza Team Tab in the user listing (this is also the place where challenges are advertised).
These users carry the badge of the challenge. It is grayed out until the user accomplishes the challenge. Should the user drop out of the challenge, the badge is removed again. In higher plans the badge can be uploaded, otherwise you can pick one from the list of provided badges.

Challenge overview

A user stays in the challenge by giving the configured number of kudos every week.
At the end of a week, Kudozza will remind every challenge participant who is still missing the kudos for the current week that he needs to give them in order to stay in the challenge.

If the user gives no kudos for a week, s/he drops out of the challenge. Except, s/he has some “skipweeks” left:
The longer the challenge, the more likely it is that users go on vacation or become sick or are temporarily too busy to give kudos.
Therefore, it is possible to configure “skipweeks” within a challenge. This is the number of weeks during a challenge in which a user does not need to give a kudos but remains in the challenge.