My Groups
What this screen is for
My Groups lists the groups you belong to. Groups establish ownership — of components, systems and projects — and are how the catalog knows which team is responsible for what.
Groups are not how permissions are granted. That is roles, and confusing the two is the most common misunderstanding about access in Fenwave.
Before you start
| To do this | You need |
|---|---|
| See your groups | signed in |
You cannot add yourself to a group. Membership requires
platform-settings.user.assign-group, which an administrator holds.
Opening it
- My Space › My Groups in the sidebar.
Direct URL: /my-groups
The interface
📸 Screenshot Placeholder: My Groups listing two groups. Mark: (1) a group entry, (2) what it owns.
| # | Control | What it shows | When you’d use it |
|---|---|---|---|
| 1 | Group entry | A group you belong to | Confirming membership |
| 2 | Owned entities | What that group is responsible for | Understanding your team’s surface |
Walkthroughs
Confirm your membership
Open the page and read the list. If a team’s group is missing, you are not in it — which affects ownership and visibility, not what you are permitted to do.
See what your team owns
Follow a group through to what it owns, or use Architecture filtered by that owner for the same question as a picture.
Scenario
Joining a team and finding out what you have taken on.
- My Space › My Groups — confirm you are in the team’s group. If not, ask an
administrator; they need
platform-settings.user.assign-group, which is a different permission from editing groups, so the first person you ask may not be able to do it. - Look at what the group owns.
- Open Architecture and filter by Owner set to your group. This is the fastest honest answer to “what am I now responsible for”, and it is often larger than the handover said.
- Check the Catalog for entries owned by your group with no documentation. Those are the ones that will page you at 3am with nothing to read.
- Note anything the team owns that nobody mentioned. Unowned or forgotten-but-owned components are exactly what a handover misses.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| You are in no groups | Nobody has added you | This page | Ask an administrator with platform-settings.user.assign-group |
| You are in the group but still cannot do something | Groups grant ownership, not permissions | Access Explorer | You need a role |
| A group owns nothing | No systems have it as owner | Projects | An administrator sets owners on systems |
| Your team’s group does not exist | It was never created | Groups | Ask an administrator to create it |
| Membership changed but nothing looks different | Session cache | — | Reload the page |
Next
- My Profile — who you are
- Architecture — what your group owns, as a graph