Settings Configuration
Settings Configuration
Hrida.ai has two separate settings areas, not one.
Hrida.ai is multi-user from day one. Even if you are the only person using it, the architecture assumes there could be many users on the same instance. That means the platform needs two layers of configuration: one for the administrator who controls the instance, and one for each individual user who controls their own experience.
Admin Settings control everything about the Hrida.ai instance itself: API connections, feature toggles, security policies, and default behaviors. Think of this as the control panel for the building. It determines what is installed and available for everyone.
User Settings control personal preferences: your default model, interface theme, language, notification preferences, and per-feature toggles for features the admin has already enabled. Think of this as the thermostat in your own room. You can adjust things for yourself, but only within what the building provides.
Many features follow a two-layer pattern:
Example: Autocomplete (AI-powered typing suggestions)
If an admin disables a feature globally, users cannot enable it for themselves. The admin setting is always the ceiling.
This pattern applies across web search, image generation, direct connections, code interpreter, and more. The admin controls what is possible. Users control what they want.
| Admin Settings | User Settings | |
|---|---|---|
| Scope | Entire instance (all users) | Individual user only |
| Access | Admins only | Everyone |
| Controls | API connections, feature toggles, security, defaults | Theme, default model, personal preferences |
| Override behavior | Cannot be overridden by users | Can customize within admin-allowed boundaries |
Check whether the admin has enabled it globally first. Your personal toggle only takes effect if the admin has made the feature available at the instance level.
Admin Settings > Connections. These are instance-wide and shared by all users.
If the admin has enabled Direct Connections, you can add personal API keys in User Settings > Connections. See Direct Connections.
Model-level settings configured by admins in the Workspace take precedence over personal settings. See Chat Parameters for the full precedence hierarchy.
Start with Admin Settings > Connections to connect your model providers (Ollama, OpenAI, etc.), then explore Admin Settings > Interface to enable or disable features for your users.