Users and User Groups — Overview

RAGFish provides Users and User Groups to help administrators manage who can access the system and which resources they are allowed to use.

As organizations adopt RAGFish, more people begin using it — employees from different departments, teams, and roles. Not everyone needs access to the same information. For example, an HR employee may not need access to Finance data, and a Sales employee may not need access to internal IT documentation. To handle this, RAGFish uses two core concepts: Users and User Groups.

What is a User?

A User represents an individual person who uses RAGFish. Each user has their own login and identity within the system, and can be assigned specific access to channels, chat assistants, or other resources based on what their role requires.

What is a User Group?

A User Group is a collection of users who need similar access or permissions. Instead of configuring access for each person separately, administrators can group users together — for example, by department, team, or role — and apply access settings to the entire group at once.

Once created, a User Group can be mapped to the required channels or resources. Any user added to that group automatically inherits the access assigned to the group, and any user removed from the group loses that access.

Example

RAGFish
   │
   ├── User: John (Finance)
   ├── User: Sarah (HR)
   ├── User: Mike (Sales)
   │
   ├── User Group: Finance Team
   │        ├── John
   │        └── (other finance employees)
   │
   ├── User Group: HR Team
   │        └── Sarah
   │
   └── User Group: Sales Team
            └── Mike

In this setup:

1. John, as part of the Finance Team, can access the Finance Channel.
2. Sarah, as part of the HR Team, can access the HR Channel.
3. Mike, as part of the Sales Team, can access the Sales Channel.

Why This Matters

Using Users and User Groups together allows RAGFish administrators to:

1. Control exactly who can access which information
2. Keep sensitive data restricted to the right people
3. Scale access management easily as the organization grows
4. Avoid manually configuring permissions for every individual user

This foundation makes it possible to build a secure, well-organized RAGFish environment where the right people always have access to the right knowledge.