Docs

Settings

What this screen is for

Settings is where the platform itself is configured: who can use it, which Git repositories and CI/CD providers it talks to, which clusters it deploys to, and how it is branded. Everything else in Fenwave consumes what is set here — a deployment cannot run until a cluster is registered, and a pipeline cannot start until a repository is connected.

It is organised as six areas, reachable from the Settings entry at the bottom of the sidebar.

Area Use it when you want to…
General Change the logo, support contact, or license key
People & Access Add a user, create a group, grant or revoke permissions
Development Connect a Git repository, a CI/CD provider, or a project
Infrastructure Register a cloud account, a cluster, an environment, or object storage
Config Export/Import Copy a working configuration to another install
Access Explorer Find out why a specific user cannot do something

Before you start

Settings appears in the sidebar if you hold any platform-settings.*.read permission. Each area then checks its own permission, so it is normal to see Settings but only some of its tabs.

If you cannot see Settings at all, you hold none of them — ask an administrator to add you to a role that does. This is a permission gate, not a fault.

Opening it

  1. Click Settings at the bottom of the sidebar.
  2. Pick an area from the submenu.

Direct URL: /platform-settings/general (the Settings entry redirects here).

The interface

📸 Screenshot Placeholder: The Settings submenu expanded in the sidebar, with the six entries visible and General selected. Mark: (1) the Settings sidebar entry, (2) the submenu, (3) the content area.

# Control What it does When you’d use it
1 Settings sidebar entry Opens the area and expands the submenu Every time
2 Submenu Switches between the six areas Moving between configuration jobs
3 Content area The selected area, usually with its own tabs across the top Doing the actual work

Most areas add a second level of tabs inside the content area. People & Access has four, Development five, Infrastructure four.

Walkthroughs

There is no task performed on this page itself — it is a hub. Follow the area page for the job you are doing.

Scenario

Setting up a brand-new Fenwave install. The order matters, because each step depends on the one before it:

  1. General — apply the license key, or nothing else unlocks.
  2. People & Access — add the administrators who will do the rest of the setup.
  3. Infrastructure — register a cloud account, then a cluster, then the environments on it.
  4. Development — connect the Git repositories and the CI/CD provider.
  5. People & Access again — now that clusters and environments exist, create the roles that scope developers to them.

Doing step 5 before step 3 is the usual first-day mistake: environment-scoped policies cannot reference an environment that does not exist yet.

When it doesn’t work

Symptom Cause Fix
Settings is not in the sidebar You hold no platform-settings.*.read permission Ask an admin to add you to a role that grants at least one
Settings is visible, but an area is missing from the submenu That area’s read permission is not granted Same — the missing area names the permission on its own page
A permission was granted but the menu has not changed Permission results are cached for the session Reload the page
Access Explorer is missing although you are in Settings It is admin-only, and separate from the Settings gate Ask an administrator to run the lookup for you

Next