Overview
Self-service is a developer portal on top of the LLM Gateway. Developers get their own API keys, open the apps they are allowed to use, copy app templates into apps they own, and ask for more when they need it. You set the limits once, instead of minting a key for every person.
The three questions you answer
Everything you configure answers one of three questions. The console's How self-service works panel uses the same structure.
Concepts
Names in the API and the developer portal
The admin screens were renamed. The API keeps its names, and the developer portal still uses some of the older words.
Abilities
Each app has its own allow and deny list for every ability, by email or Smart Group. An access plan then sets each ability to Always, Only if the app allows or Never.
How a decision is made
The gateway decides one person's access to one app in this order, on every portal page and on every call made with a personal key.
- Suspended? A suspended person gets nothing, whatever else says yes.
- Find their access plan. A plan matches when the person is in one of its Smart Groups. When several plans match, the plan whose matching group has the lowest rank wins (ties go to the plan name). Plans never combine. A person with no plan follows the rule for people without a plan: Keep each app's own settings (the default) or No self-service.
- Add up the yeses. The plan's Always abilities, plus the app's own allow lists, plus approved requests, plus what they own.
- Remove the noes. Anything the app's own lists deny them. A deny always wins; a deny on Viewer access removes every ability on that app.
- Apply the plan's limit. Anything the plan marks Never, and any app outside the plan, is dropped. Without Viewer access, nothing is left.
An app someone copied from a template is not capped by their plan's app or ability limit. Suspension, No self-service, the app's own denies and the plan's model and key limits still apply.
To see the result for one person, use Check what someone gets on the Overview tab or Check a person on the People tab. See Check what someone gets.
Personal and shared keys
Each app uses one of two credential modes. The mode decides which keys people receive. It does not decide who has access.
A personal key is a full gateway credential. Use it anywhere you would use a Quilr key:
sk-quilr-ss-<48 hex characters> new personal keys
sk-quilr-<app key>:ss1.<identity>.<id> older personal keys, still accepted
New keys are random and contain neither the app key nor the owner. Keys created before the new format keep working unchanged.
A personal key works only while:
- the app is on Personal API keys (switching an app to a shared key stops every personal key for it),
- the key is active and not past its expiry,
- its owner still holds Viewer access on the app and is not suspended.
When access is removed, the key stops within about a minute, once the gateway's access cache refreshes. Smart Group membership changes also take effect within about that time. A person leaving your directory does not stop their keys by itself; remove their access or suspend them. See Offboard someone.
Limitations
- Shared keys are not personal. Removing someone's access to an app on a shared key hides the app from them, but a key value they already copied keeps working. Rotate the app's keys.
- Model options apply to personal keys only. The app's main key, its shared keys and JWT sign-ins are never limited by a plan's model options.
- Keys per person. A person holds at most 10 active personal keys per app. An access plan can lower that, and a key's lifetime is capped by the shorter of the app's and the plan's maximum.
- App templates need app-independent policies. An app cannot be a template while any guardrail policy depends on its identity (its name or id), because those policies would not cover the copies. The console lists such policies.
- The Users view and API show app lists only. The Users API shows access granted by each app's own lists and personal keys, not access granted by an access plan. Use Check a person for the full answer.
- Changes are not instant. Saved settings reach every gateway server within a configuration sync, and personal keys then follow within the access cache lifetime (about a minute).
Local MCP tools
The developer portal also has MCP Gateway, where people connect their AI app to permitted local MCP tools. See Connect your AI app. When no tools are permitted, administrators get a Manage MCP access shortcut; see Manage MCP access.
Related
- Admin guide - set up self-service, step by step.
- Access plans - what each plan gives and how to roll it out.
- Developer guide - the developer portal.
- Smart groups - the groups and ranks plans match on.
- Audit Log - review settings change requests and roll back changes.