User accounts and access control on a private AI server
Last updated
User accounts and access control on a private AI server should give every person their own login and keep admin rights to one or two people. Olares One has separate accounts with three roles, and each person connects with the LarePass app.
Olares One → Private AI server → Local models · accounts · backups → Company data stays in the company
Why not share one login?
A shared login hides who asked what and makes it impossible to cut off one person without locking out everyone. Separate accounts fix both problems. They also let you remove a leaver's access on their last day, which matters more once the server holds client or staff data.
Separate accounts also make internal rules enforceable. A rule that only the finance team may upload payroll files means nothing if everyone signs in as the same user.
How does Olares One handle user accounts and access control?
Olares One is a multi-user system. Each person gets a separate account and connects with the LarePass app, and Olares' FAQ lists three roles, Super Admin, Admin and Member. The person who activates the box becomes Super Admin, so choose that person with care before you start.
| Role | What it does, per Olares' FAQ |
|---|---|
| Super Admin | Activates the system and manages admins |
| Admin | Performs cluster-level tasks |
| Member | Uses shared services |
Olares' product page also lists configurable multi-factor authentication for sensitive operations, and sandboxed apps with their own resource limits.
What access plan suits a small business?
We recommend two admins, everyone else a Member, and no shared logins. One admin is a single point of failure, and more than two spreads rights too wide for a small team. A business with an outside IT provider might reasonably add that provider as a third admin.
- Pick a Super Admin who is likely to stay with the business.
- Name one backup Admin.
- Turn on multi-factor authentication where Olares offers it.
- Write down how you remove an account when someone leaves.
- Decide whether Members may reach the box from outside the office. See what leaves a private AI server.
What should you ask before go-live?
Some access questions only Olares or the chat app can answer. Ask Olares whether the system logs sign-ins and admin actions, and for how long. Check how the chat app you install stores chat history, and whether admins can read other users' chats.
The answers belong in your data-protection records. Capacity is the other half of access. In Olares' own test, the box handled 8 concurrent requests at about 81 tokens/s each with qwen3-30b-a3b. For sizing, read the on-premise LLM server guide.
If the chat app lets admins read every chat, tell staff before go-live.
Questions & answers
How many user accounts can Olares One have?
The Olares pages we read do not state a limit. The practical limit comes from the model and how many people ask at once. In Olares' own test the box served 8 concurrent requests on qwen3-30b-a3b at about 81 tokens/s each.
Do staff need an app to sign in?
Yes. According to Olares' FAQ, each person connects with the LarePass app.
Sources for this entry
- Olares One FAQ (Olares docs) (Company-published)
- Olares One product page (Company-published)
- Olares blog: local AI hardware benchmarking (Oct 2025) (Company-published)
Continue this reading path
How the related websites connect
Cite this entry
Best Private AI Server. “User accounts and access control on a private AI server.” Content reviewed 13 November 2026.
https://bestprivateaiserver.com/private-ai-user-accounts/