Skip to main content

View History

AI-Public offers the possibility to set per role whether the chat history of users or employees is visible. This can be configured in the admin section under Permissions.

User Chat History​

The chat history of users is by default visible to authorized managers or administrators (for example, Employees with management tasks, Location Admins, Environment Admins) in the overview of users per team/department. If this is not desirable due to privacy considerations of the organization, the view of the history can be turned off for the roles:

  • Employee (insofar as they have management/view rights)
  • Location Admin
  • Environment Admin

Employee Chat History​

The chat history of employees (and other users) is by default visible to higher administrator roles in the account overview. If this is not desirable due to privacy considerations of the organization, the view of the history can be turned off for the roles:

  • Location Admin (depending on configuration)
  • Environment Admin

In the Accounts overview in the admin section, the history of employees and users is always visible to authorized Super Admins and Environment Admins.

Additionally, access to the Accounts overview can be completely closed for specific admin roles (such as Location Admin) by editing the visibility of the Account tile in the Tenant rights.

In the overview of users per team/department, managers (e.g., Employees with management tasks, Location Admins) can track activity. This can be disabled for privacy considerations.

In the overview of assistants, the Employee (or an administrator such as Location Admin or Environment Admin) has insight into chats related to their own assistants or assistants within their scope. This can be disabled for privacy considerations.

Server Security​

The view settings only affect the User Interface of the front-end application. Turning off buttons on the User Interface does not provide 100% protection. If you want to completely exclude certain roles from viewing the chat history of others, it is best to edit the rights on the Tenant database for chats and chat messages:

  • Chats -> give rights only to own records (or specific shared/controlled records)
  • Chat messages -> give rights only to own records (or specific shared/controlled records)

It is recommended to implement both methods, as it can be strange to have a history button that then gives an error message because the server rights are missing.