Check platform-wide settings

What this achieves

Two screens in this console show how the platform itself is configured, rather than how any one customer is. Both are reference views: they answer what a default is, and neither of them changes it.

Required role: Humavera platform staff.

Steps

Go to Platform → System Settings.
Read the tab that covers what you are checking: General, Security, Notifications, AI, or Infrastructure.
Go to Platform → AI Configuration for how AI features are routed.
Read Model Routing, Available Models, and Configured Providers.

Nothing on these screens is editable

Every field on both screens is shown read-only, including the switches. They are a window onto the running configuration, not a control panel, and the screen says so at the top.

A platform-wide default is part of how the deployment is built, so changing one is an engineering change rather than something anybody switches on from a page. That also means nobody can alter the platform’s behaviour for every customer by clicking through this console.

What each tab covers

Option	Description
General	Platform identity, the default timezone, and the defaults a new workspace starts with.
Security	The password policy and session rules in force across the platform.
Notifications	How platform email is configured and which notification channels are on by default.
AI	The default models behind AI features and which AI features are available platform-wide.
Infrastructure	Maintenance mode, how rate limits are derived, and the data retention periods.

Platform settings are not a customer’s settings

These are defaults for the platform. What a given customer’s workspace actually uses is set inside that workspace, by their own administrators, and their settings override the defaults where the two overlap.

Example: the platform has a default timezone and a default language. HC Corp sets Europe/London and English in their own workspace, and that is what their people get regardless of what the platform default is.

If a customer asks for a change to something in their workspace, the answer is their own settings, not this screen.

AI routing

Platform → AI Configuration shows which model each AI feature is routed to and at what tier, the models available, and which AI providers are configured. Routing is set in the deployment, so like the settings screens it is read rather than changed here.

No credentials or secrets are shown on this screen. It reports which providers are configured and nothing about how they are reached. Where a provider is not configured, the feature that depends on it degrades rather than failing — it goes quiet instead of breaking a customer’s screen.

Per-workspace AI behaviour — which AI features a customer has on, and their own model and confidence preferences — belongs to their own settings, and the screen links across to them.

What happens next

These screens answer questions rather than change anything. Where the answer is that a customer needs something different, the change belongs either in their own workspace settings or in what their plan entitles them to, which is set on their workspace record.