Overview #
Members are the people in your organisation. The July 2026 release keeps role management deliberately simple: every member can manage workspaces and repositories, and one person — the organisation creator — has the additional ability to delete members and the organisation itself.
Where to manage members #
Open Organisation Settings from the sidebar workspace selector and scroll to the Members section. You’ll see:
- A table with every member: avatar, name, email, role, join date.
- A + Invite member button in the top right.
- A footer row showing the member count and a note: “Roles are assigned automatically.”
The Members section is available on the Pro tier. On Free, the section is shown for visibility but inviting is disabled with a tooltip pointing to upgrade.
Roles #
Norma keeps roles minimal in this release:
| Role | Who has it | What they can do |
|---|---|---|
| Owner | Every member | Create / rename / delete workspaces, import / move / remove repositories, run scans, manage MCP connections, view billing. |
| Admin | The organisation creator only | Everything Owner can do, plus invite new members, remove members, and delete the entire organisation. |
In the product UI:
- Every member’s table row shows the Owner chip in the Role column.
- The admin’s row additionally shows the Admin chip in the Actions column.
- The current viewer’s row has a small you label after their name.
There’s no per-workspace or per-repository role yet — every member sees every workspace and every repository. Finer-grained roles are on the roadmap.
Inviting a member #
Requires Admin role.
- Open Organisation Settings → Members.
- Click + Invite member.
- Enter the email address of the person to invite.
- Click Send invite.
The invitee receives an email with a sign-up link. When they click it, they sign in with their Google / GitHub / Bitbucket identity (see Sign up) and are automatically added to your organisation as an Owner.
Pending invitations are shown above the member table with a Resend and Revoke action.
Removing a member #
Requires Admin role.
- Open Organisation Settings → Members.
- Find the member’s row.
- Open the kebab menu on the right.
- Choose Remove from organisation.
- Confirm.
The member loses access immediately on their next request. Their work stays — the workspaces they created and the repositories they imported remain in the organisation. Only the person is removed.
The admin cannot remove themselves while they are the sole admin. To leave, they’d have to delete the whole organisation (see Delete account).
Changing who is admin #
Admin transfer is not supported through the product in the July 2026 release. The organisation creator is the admin for the lifetime of the organisation. If you need to change this — for example because the original admin has left the company — contact support; we can re-assign in the database for now.
Self-service admin transfer is on the roadmap and will land before the Team tier ships.
Why this is deliberately simple #
The role model in the July release prioritises two things:
- Every member can get work done — no asking an admin to create a workspace or run a scan for them. The day-to-day surface is the same as if everyone were an admin.
- Destructive actions are gated. Deleting members or the entire organisation lives behind a single non-transferable role. A compromised or careless Owner cannot wipe the account.
Richer role structures — for example a Workspace Owner who manages only their workspace’s settings — are planned for the Team tier, which is a later release. The July tier set (Free, Pro) keeps it to this two-role model on purpose.
Frequently asked questions #
Can I see who created a particular workspace or repository? #
Yes. Each workspace shows the creator below its name; each repository carries the importer’s name in its detail view.
Can a member be in multiple organisations? #
Yes. Switch organisations from the workspace selector in the top-left of the sidebar (Pro tier only).
I removed a member and they still seem to be able to log in. #
They can sign in to their Google / GitHub / Bitbucket identity, but they no longer have access to your Norma organisation. They’d land on the join-workspace screen with no organisation to enter unless they belong to a different one.
Can I see when a member last logged in? #
Not in the July release. Activity logs and last-login timestamps are on the roadmap.
Related #
- Workspaces — what every member can manage.
- Plan and billing — inviting members is a Pro-tier feature.
- Delete account — the only thing only Admin can do beyond member management.
