Docs

Access the Platform

What this page is for

How to get into Fenwave, and why what you see may differ from a colleague. This is the page to read before concluding something is broken.

Before you start

An administrator must have created your user record. Fenwave has no self-registration: you cannot create an account, and you cannot edit your own profile.

Your record must carry the exact username and email of your GitHub or Bitbucket account. A mismatch is the single most common reason a new user cannot sign in.

Opening it

  1. Go to the Fenwave URL your organisation provides.
  2. Sign in with GitHub or Bitbucket.
  3. Your profile is created from that account on first sign-in.

The interface

What you see is decided by permissions, applied per menu entry:

You see Because
Explore You hold catalog or TechDocs read
Build You hold scaffolder or App Builder access
Deploy You hold access to at least one environment tier
Cost You hold access to at least one tier
Object Storage You hold the Object Storage read permission
Tools You hold at least one tool’s access permission
Settings You hold any platform-settings.*.read permission
Access Explorer You are an administrator — gated separately from Settings

A missing menu item is a permission, not a bug

This is the design. Two people with different jobs should see different platforms. The exception is Pipeline Builder, which is deliberately greyed out and labelled “(Soon)” for everyone — it is not released, and there is nothing to grant.

Permission results are cached for your session. A permission granted a moment ago may not appear until you reload the page — the most common false report of “the permission didn’t work”.

Walkthroughs

Sign in for the first time

  1. Ask an administrator to add you, giving them your exact Git username and the email on that account.
  2. Sign in with the matching provider.
  3. Check My Profile shows the account you expect.

Work out why you cannot see something

  1. My Profile — right account?
  2. Reload the page — session cache.
  3. Ask an administrator to check Access Explorer, giving them the exact permission string from the error and your username.

Scenario

A new joiner cannot sign in on their first morning.

  1. Confirm an administrator actually created the record. “I sent them a message” is not the same as the record existing.
  2. Compare the email on the record with the email on their Git account. They must match exactly — this is the cause the majority of the time, and it presents as a generic sign-in failure with no useful message.
  3. Check the username too: it must be the Git username, not a display name or an email prefix.
  4. If sign-in then works but the platform looks empty, no role was assigned. Adding a user and giving them a role are two separate steps, and it is easy to do the first and forget the second.
  5. Have them reload after the role is granted, because of the session cache.

When it doesn’t work

Symptom Cause How to check Fix
Sign-in fails No user record, or email does not match the Git account The user record An administrator adds or corrects it
Signed in, platform is empty No role assigned, or the role carries no policies Access Explorer Assign a role that carries policies
Menu changed for a colleague, not you Session permission cache — Reload the page
You see a tier but cannot act in it You hold .access but not the action permission Access Explorer Ask for the specific permission
Pipeline Builder is greyed out Not released — Expected for everyone

Next