Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1870] [FEAT]: Enable multi-user on boot #1217

New Issue
Open
opened 2026-02-22 18:23:45 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:23:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @ajferrario on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1870

What would you like to see?

As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to set the admin username and password for the initial Admin user in each environment manually before I can create the API key and use the API to configure the needed users, workspaces and other features for that environment.

I'd like to have a fully-automated and hands-off deployment option, and this is one of the main manual steps blocking me from achieving this.

I will file other issues for a couple other things needed for fully-automated deployments.

Originally created by @ajferrario on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1870 ### What would you like to see? As an anythingllm administrator attempting to deploy a number of anythingllm environments, I currently need to set the admin username and password for the initial Admin user in each environment manually before I can create the API key and use the API to configure the needed users, workspaces and other features for that environment. I'd like to have a fully-automated and hands-off deployment option, and this is one of the main manual steps blocking me from achieving this. I will file other issues for a couple other things needed for fully-automated deployments.
yindo added the enhancementfeature request labels 2026-02-22 18:23:45 -05:00
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@ajferrario commented on GitHub (Jul 15, 2024):

@timothyasp if you'd prefer I'll rename this to enable automated deployment for multi-user environments. I wasn't sure how much content you would like in one FR so I started it out at a granular level.

@ajferrario commented on GitHub (Jul 15, 2024): @timothyasp if you'd prefer I'll rename this to enable automated deployment for multi-user environments. I wasn't sure how much content you would like in one FR so I started it out at a granular level.
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 15, 2024):

If anything, in my mind this request makes sense as just one FR, because they are all really close in scope since if we enable multi-user on boot you probably also want to make users and such - let's just keep it one issue for now and if scope grows then we can break it out where it makes sense 👍

@timothycarambat commented on GitHub (Jul 15, 2024): If anything, in my mind this request makes sense as just one FR, because they are all really close in scope since if we enable multi-user on boot you probably _also_ want to make users and such - let's just keep it one issue for now and if scope grows then we can break it out where it makes sense 👍
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@dannysteenman commented on GitHub (Oct 21, 2024):

+1 for this feature!

@dannysteenman commented on GitHub (Oct 21, 2024): +1 for this feature!
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 21, 2024):

@dannysteenman How would this flow work for you - any places you envision and improvement:

  • Boot AnythingLLM with some specific ENV variable(s) set
AUTO_CREATE_ADMIN=1
AUTO_CREATE_ADMIN_CRED="username:password"
  • This creates an admin role user with username username and password password.

Now the instance is in multi-user mode and the instance has a single admin user that can be used now?

@timothycarambat commented on GitHub (Oct 21, 2024): @dannysteenman How would this flow work for you - any places you envision and improvement: - Boot AnythingLLM with some specific ENV variable(s) set ``` AUTO_CREATE_ADMIN=1 AUTO_CREATE_ADMIN_CRED="username:password" ``` - This creates an admin role user with username `username` and password `password`. Now the instance is in multi-user mode and the instance has a single admin user that can be used now?
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@dannysteenman commented on GitHub (Oct 22, 2024):

@dannysteenman How would this flow work for you - any places you envision and improvement:

  • Boot AnythingLLM with some specific ENV variable(s) set
AUTO_CREATE_ADMIN=1
AUTO_CREATE_ADMIN_CRED="username:password"
  • This creates an admin role user with username username and password password.

Now the instance is in multi-user mode and the instance has a single admin user that can be used now?

I would say that if you supply this var: AUTO_CREATE_ADMIN_CRED it would determine you'd like to setup multi-user mode so I guess you can leave this var: AUTO_CREATE_ADMIN out.

and then next to that maybe have the ability to generate an API key yourself and assign that to this admin instead of generating it via the webui

@dannysteenman commented on GitHub (Oct 22, 2024): > @dannysteenman How would this flow work for you - any places you envision and improvement: > > * Boot AnythingLLM with some specific ENV variable(s) set > > ``` > AUTO_CREATE_ADMIN=1 > AUTO_CREATE_ADMIN_CRED="username:password" > ``` > > * This creates an admin role user with username `username` and password `password`. > > Now the instance is in multi-user mode and the instance has a single admin user that can be used now? I would say that if you supply this var: AUTO_CREATE_ADMIN_CRED it would determine you'd like to setup multi-user mode so I guess you can leave this var: AUTO_CREATE_ADMIN out. and then next to that maybe have the ability to generate an API key yourself and assign that to this admin instead of generating it via the webui
yindo commented 2026-02-22 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@w4zu commented on GitHub (Jul 21, 2025):

+1

@w4zu commented on GitHub (Jul 21, 2025): +1
yindo changed title from [FEAT]: Enable multi-user on boot to [GH-ISSUE #1870] [FEAT]: Enable multi-user on boot 2026-06-05 14:39:35 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1217
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?