Overview
By default, every newly released model is set to private. This article covers three changes that keep your model list current and your access controlled: hiding outdated models, granting models by tier, and limiting sharing.
Model names below reflect the current AI CTRL Ratecard. Check it when new models are released, and see Available Models for what each one is suited to.
Hiding Outdated Models
Keep only the newest generation from each provider visible. Older models stay on the platform but are hidden, which keeps model lists short and steers users to current models.
| Provider | Keep visible | Hide |
|---|---|---|
| OpenAI | GPT-5.6 Luna, Terra, Sol | GPT-4.x, GPT-4o, GPT-5 through GPT-5.5 |
| Anthropic | Claude Opus 5, Sonnet 5, Haiku 4.5 | Claude Opus 4.5 through 4.8, Sonnet 4.5 and 4.6 |
| Gemini 3.7 Flash | Gemini 2.5 family, Gemini 3 and 3.1 Flash, Gemini 3.5 Flash |
- Go to Admin Panel → Settings → Models.
- Find the model to hide, click the ellipsis (...) at the end of its row, and select Hide.
- To hide many models at once, narrow the list with the view filter or search, then use the Actions menu to hide every model currently in view.
Important: Use Hide rather than making an outdated model private. Hiding removes a model from the selector for everyone but keeps it reachable, so any custom model built on it keeps working. Restricting the model instead breaks those custom models with a Model not found error.
Setting Model Access
Group the remaining models into tiers and grant each tier to the users who need it. Routing routine work to the Basic tier keeps credits stretching further, while the most capable models stay available for the tasks that need them.
| Tier | Models | Intended users |
|---|---|---|
| Basic | GPT-5.6 Luna, Claude Haiku 4.5, Gemini 3.7 Flash | All staff by default |
| Mid | GPT-5.6 Terra, Claude Sonnet 5, Gemini 3.1 Pro | Analysts, developers, and teams doing daily analysis or coding |
| Top | GPT-5.6 Sol, Claude Opus 5 | Small group with an approved need for frontier work |
- Go to Admin Panel → Users → Groups and create a group for each tier, named Basic, Mid, and Top.
- Set each group's visibility to No one, so it stays out of users' sharing menus.
- Add users to their tier. Tiers are cumulative: add Mid users to Basic as well, and Top users to all three.
- Go to Admin Panel → Settings → Models and open a model.
- Set its visibility to Private, then add the matching group under Access Control.
- Click Save & Update, then repeat for each model.
Note: A custom model a user builds sits on top of a base model, so the user needs access to that base model as well. Keep this in mind when restricting a model to one tier, since users outside that tier cannot use custom models built on it.
Tip: To confirm the result, use Preview Access in the user list, the eye icon at the right of each user row. It shows every model that user can reach.
Setting Sharing Permissions
Sharing permissions control what users can publish to others. The safe default is to allow sharing inside the instance and keep public sharing off.
- Go to Admin Panel → Users → Groups and open Default Permissions.
- Turn off every public sharing option, so nothing is published beyond the instance.
- Leave internal sharing on for the resources users collaborate on, such as models and knowledge.
- Click Save.
Note: Preview Access appears on User and Pending rows only. Admin accounts bypass access control, so no preview is shown for them.