[Feature Request]: User Management and Role-Based Access Control (RBAC)

[rplescia]

Is there an existing issue for the same feature request?

• [X] I have checked the existing issues.

Is your feature request related to a problem?

No

Describe the feature you'd like

As an administrator, I want to have the ability to add/manage/remove a user's ability to access the application and control what features in the app they can use via roles so that it can be deployed in an organisation with more security restrictions. I also want to hide some features from less technical users to avoid confusing them with too much information.

New 'Admin' page for managing 'Users', 'Teams' and 'Roles'

• Users: Admin users can add new users to the system using their email addresses, once added, the system generates an invitation email to the user with a link, the link should take the user to a page where they are asked to set a strong password. Also, Admins can modify/delete users.
• Teams: Admin users can create Teams, add users, and assign teams to roles.
• Roles: Admin users can create/modify/remove Roles. Roles are used to restrict access to knowledge bases or system features such as 'Agent'.

3 System Roles that come 'out-of-the-box'

1. Administrator: Full access
2. Power User: Full access excluding the ability to add/change/remove users, teams and roles.
3. Standard User: Access to all features excluding:

• Add/modify/remove users, teams and roles.
• Add/modify/remove model providers
• 'System' Page is hidden from view

Describe the implementation you've considered

No response

Documentation, adoption, use case

No response

Additional information

No response

[meltedhead]

Seconded. I have just been trying to test this out myself. I want to limit what users can see and do.

[ProfessorX]

I second it.

It's very useful for enterprise users.

[HerzogVolpe]

i second it. without any way to restrict the newly registrated users, you can get a real bot problem...

[galovics]

This is actually a much needed thing. I'm not yet sure how you can get users invited into a RAG system without exposing every single piece of detail of the system without building a custom UI entirely.

[snazzer]

Agreed, without admin control this isn't really deployable in a production setting.

[galovics]

I mean the two alternatives I see for a production deployment are:

• you develop an entirely custom frontend while RAGFlow's current deployment serves as an admin UI + the backend components for RAG
• if you wanna use the Agent mechanism, you can create the agent and embed it as an iframe into a custom frontend

[which-W]

@ProfessorX Thanks a lot for your suggestion — and apologies for the delayed response! ⏳

We've implemented basic team management in the open-source version, and full team permission control is available in the commercial version 🔐. If your use case requires advanced access management, feel free to reach out to the RAGFLOW Assistant for commercial-level support.

If this addresses your needs, please consider closing the issue when you get a chance. Otherwise, we’ll plan to close it during our next round of maintenance.

Appreciate your continued interest and input — we’re excited to keep improving with your feedback! 🚀

[rplescia]

So you've taken my idea and commercialised it... Not very nice when this is supposed to be an OPEN-SOURCE project!

[galovics]

@which-W I might have missed something but I didn't even know you have a commercial version. There's nothing on the website, nothing here in the readme. Is there a plan to monetize the open-source product just like any other SaaS out there?

[which-W]

@rplescia Thanks for sharing your thoughts, and sorry for any confusion caused. Just to clarify — our implementation of team permissions is quite different from the structure you mentioned, and it's something we've been exploring independently based on long-standing user needs.

RAGFlow is a hybrid open- and closed-source product, built and maintained by a dedicated team 🚀. We really appreciate your feedback, and we'd love to have you involved in helping shape its future. Contributions, ideas, and discussions are always welcome! 💬✨

Thanks again for engaging with us!

[which-W]

@galovics Thanks for your interest! Yes — our project includes components designed for commercial collaboration 🤝. If you're interested in learning more or exploring potential opportunities, feel free to join our Discord where we share updates and handle partnership inquiries 💬✨.

Looking forward to connecting with you there!

[rplescia]

This is totally not cool! At no point in this project's history has it been published that this project has a commercial angle to it until now. Now you take the community's work and try to make money off it... not cool! I will no longer contribute my ideas to this project.