Secure the appliance
Protect who can call a surface, who can administer the appliance itself, and the credentials it holds on your behalf. Field-level reference for every mechanism here is in Source authentication →, Secrets →, and RBAC →.
| Guide | What you will achieve |
|---|---|
| Validate bearer tokens on a surface | Create a JWT verification strategy and attach it to a surface so only callers with a valid, correctly issued token can reach it. |
| Rotate provider credentials without downtime | Point a surface’s LLM node at a new secret holding the new provider credential, confirm it works, then retire the old secret, so every surface keeps working while you rotate. |
| Limit dashboard actions with RBAC roles | Assign the Administrator, Power User, or User role to a dashboard account so it can only perform the actions its job requires. |
| Require terms acceptance before dashboard access | Publish your organisation’s terms and conditions from the T&C Manager, so every dashboard user accepts them at sign-in, and ask existing users to accept again when a new version is published. |
Was this page helpful?
Glad to hear it. Thanks for letting us know.
Sorry to hear that. Thanks for letting us know.