Configuration
You set the platform's theme, see which configuration settings are defined on the platform, each one's value on the platform and where that value comes from, and you set the platform's own values.
The platform's theme
Inlorus's colours come from Projera UI's theme. Under Theme, the theme set here is the same for every account and tenant; each person can change it for themselves in My Preferences. Until one is set, Projera UI's default theme applies.
| Setting | What it changes |
|---|---|
| Palette | The colours the theme is built from, from Projera UI's catalogue. The squares beside it are the palette's colours. |
| Centre tone | The palette colour the theme is built around; The palette's suggestion leaves the choice to the palette. |
| Contrast | How far grounds and texts stand apart: Low, Balanced, High or Inverted. |
| Material | How surfaces and their corners look: Opaque, Glass, Gradient, Line or Paper. |
| Frame | How the side menu stands apart from the page. |
| Colour amount, Colour distribution | How much colour the grounds carry, and how it is spread over them. |
| Light | How light the screens are: Light, Tinted, Deep or Dark. |
| Marker | Which colour shows selection, focus and links: the centre tone or the accent. |
- Choose each setting.
- Press Set the Platform's theme. Every signed-in page shows the new theme at its next load.
Every text keeps a readable contrast with its ground in every combination; the theme works that out, not this screen. So does the logo in the menu and on sign-in: navy letters on a light, neutral ground, white on a dark one, text colour on a coloured one. The theme is stored as the platform value appearance.theme; every change is written to the platform's audit trail. Setting it requires config.write on the platform. The public site keeps its own colours.
What's on this screen
The line at the top says how many definitions there are, how many values sit in the platform's own record and how many keys have no definition. Each row shows the key, value type, sensitivity, description, value, the scopes in which it can be changed and the time of the last change.
Where the value comes from
| Label | Meaning |
|---|---|
| set here | The value comes from the platform's own record. |
| definition default | There is no record on the platform; the definition's own default applies. |
| no value | There is neither a record nor a default. |
| undefined key | The record has a value but there is no configuration definition. |
Tip Settings defined as secret and keys whose names look like credentials are never shown under any condition; the value reads secret.
Setting a value at the Platform
- Under Set a value at the Platform, choose the Key, or A new key… and type it as
namespace.name(for exampleeducation.default_course_credits). - Type the Value as JSON: a number as
5, text in quotes as"text", yes or no astrueorfalse. - Press Set at the Platform. The message says what was set; the row shows set here.
The value is the platform's own record: accounts and tenants inherit it unless they set their own, and a capability's Contents can carry it. Nothing sits above the platform, so no policy floor applies here. Every change is written to the platform's audit trail. The server refuses, with the reason, a key that is not namespace.name, a value that is not JSON, a key whose definition does not allow a value at the platform, and a key that names a credential (a secret is not set on this screen).
Viewing this screen requires config.read on the platform; setting a value requires config.write on the platform. A Tenant's own values are changed on the Config Management screen.