General
What this screen is for
General holds the platform’s own identity and its license: the logo users see in the sidebar, the support contact they are pointed at when something breaks, and the license key that unlocks the platform. It is the only area whose settings are visible to every user of the install, whether or not they can open Settings themselves.
Before you start
| To do this | You need |
|---|---|
| View the page | platform-settings.general.read |
| Change branding or support details | platform-settings.general.update |
| View license status | platform-settings.license.read |
| Apply or replace a license key | platform-settings.license.update |
Holding only the read permissions shows the page with its controls disabled —
that is expected, not a fault.
Opening it
- Click Settings in the sidebar.
- Click General.
Direct URL: /platform-settings/general
The interface
📸 Screenshot Placeholder: The General page showing all four sections. Mark: (1) Platform Branding with the logo preview and upload button, (2) Support Information, (3) Platform Information, (4) the License section with its status chip.
| # | Control | What it does | When you’d use it |
|---|---|---|---|
| 1 | Platform Branding | Preview of the current logo, and an upload control accepting any image type | Rebranding the install for your organisation |
| 2 | Support Information | The support email and support portal your users are directed to | Pointing users at your own service desk instead of the default |
| 3 | Platform Information | Name, version, slogan, description, documentation URL — read-only | Confirming which version you are on before reporting a problem |
| 4 | License | Status chip, License ID, last validation date, the key field, and the active-user report | Applying a new key, or checking seat usage |
Platform Information is display-only on this screen. It reflects values supplied by the platform build, so there is nothing to edit there.
Walkthroughs
Replace the platform logo
Requires platform-settings.general.update.
- Go to Settings › General.
- In Platform Branding, click the upload button.
- Pick an image file. The preview updates immediately, before saving.
- Save.
- Reload the page — the sidebar logo is served from the platform’s own storage and is cached, so it will not change in place.
Point users at your own support desk
Requires platform-settings.general.update.
- Go to Settings › General › Support Information.
- Set the support email and the support portal URL to your own.
- Save.
Apply a license key
Requires platform-settings.license.update.
- Go to Settings › General, scroll to License.
- Paste the key into License Key (JWT).
- Validate it. The status chip and Last Validated update on success.
- If validation fails, the key is not applied — the previous license stays in force. Nothing is lost by trying an invalid key.
Check how many seats are in use
Requires platform-settings.license.read.
- Go to Settings › General › License.
- Read the active-user table. Last Active tells you who is genuinely using a seat, as opposed to who merely has an account.
- Export the usage report if you need it outside the platform.
Scenario
A new client rebrands their install and takes over support.
Claude Ltd has just had Fenwave deployed. Their platform admin wants their own logo in the sidebar and their own service desk on the support link, so that developers stop emailing the vendor.
- Open Settings › General.
- Upload the company logo in Platform Branding, then save.
- In Support Information, replace the support email with their internal service-desk address and the portal URL with their own ticketing system.
- Save, then reload — the sidebar now carries their logo.
- Scroll to License and confirm the status chip reads as valid, and that Last Validated is recent.
- Check the active-user table against the seats they bought, so they find out about an overage now rather than at renewal.
Total: about five minutes, and it is the first thing worth doing on a fresh install — every other area is easier to explain to users once the platform looks like theirs.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| Upload button and fields are greyed out | You have general.read but not general.update |
Settings › Access Explorer for your username | Ask for a role granting platform-settings.general.update |
| Logo saved, but the sidebar still shows the old one | The logo is served from platform storage and cached | Hard-reload the page | Reload; if it persists, clear the browser cache |
| License section is absent | You lack platform-settings.license.read |
Access Explorer | Ask for a role granting it |
| License key rejected | Key is malformed, expired, or issued for a different install | Check the error next to the key field | Request a replacement key; the previous license is still in force |
| Platform Information shows unexpected values | It is read-only and comes from the build | — | Not editable here; check which image is deployed |
Next
- People & Access — add the team
- Config Export/Import — copy this configuration elsewhere