Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These reports provide you with the users-related statistics. You can view active users, active users sessions, visitors, and associated details.

Table of Contents

Prerequisites: users in Koji

Before using the reports, it is important to understand the general concepts of users in Koji. There are two types of users in Jira environment: Jira customers and internal Jira users. Users can have various roles, depending on the settings set by a Koji admin. There are a few notes to pay attention to:

  • A person who installed Koji gets the Koji admin role in Kbot.

  • A Koji admin can access Koji backoffice and can manage other users' roles in Koji.

  • Koji admin cannot change their own role.

  • Any new user starts to speak with the Koji in a chat as a Koji customer, as this role is granted to any new user automatically.

  • A Koji admin can grant customers roles in Configuration > Tenants > Tenant role setup by clicking Set in a corresponding line.

  • Regardless of a person's status in Jira and absence or presence of the License, each person has at least one role in Koji.

  • If Koji cannot recognize and authenticate a user, such a user is considered anonymous. In this case a user can accept Koji's offer to authenticate in order to get a role and start communicating.

  • The authentication procedure for Jira customer and Jira users is slightly different. Learn more about it here: Authentication in Slack and Microsoft Teams.

  • If a portal supports anonymous access, a user must specify their contact email. After that the user is added to the list of Jira customers with the Customer role. Learn more about anonymous portal access here: https://konverso.atlassian.net/wiki/spaces/KAJSM/pages/2872016917/Authentication+on+Atlassian+customer+portals#Anonymous-access.

Active user sessions

When a user logs in to Koji, an active session is started. The system uses tokens to collect user data, such asĀ IP addresses and user login IDs. These tokens are valid for only one session.

...