Projects
What this screen is for
The Projects tab declares what your organisation builds. A project (a system) groups components, and components are what show up in the Catalog with an owner and a type.
This is how a repository stops being an entry in a settings table and becomes something a developer can find.
Before you start
| To do this | You need |
|---|---|
| See the tab | platform-settings.project.read |
| Open a project’s details | platform-settings.project.view-details |
| Create a project | platform-settings.project.create |
| Edit one | platform-settings.project.update |
| Delete one | platform-settings.project.delete |
| Set the owning group | platform-settings.project.assign-owner |
| Link or unlink components | platform-settings.project.manage-components |
Create the owning group first — a project without an owner produces catalog entries nobody is responsible for.
Opening it
- Settings › Development
- Select the Projects tab (it opens here by default).
The interface
📸 Screenshot Placeholder: The Projects tab showing the systems table and the components table. Mark: (1) the systems table, (2) the components table, (3) the owner group column, (4) the component type, (5) the link/unlink action.
| # | Control | What it does | When you’d use it |
|---|---|---|---|
| 1 | Systems table | The projects themselves | Creating or renaming a project |
| 2 | Components table | The components, each linked to a system | Adding a service or library |
| 3 | Owner group | Which group owns the entry | Establishing responsibility |
| 4 | Component type | What kind of thing it is | Filtering the catalog usefully |
| 5 | Link / unlink | Attaches a component to a system, or detaches it | Reorganising as the estate grows |
Components and systems are two separate tables on one tab. A component can exist without being linked to a system, and will then appear in the catalog with no parent — usually not what you want.
Walkthroughs
Create a project and its first component
Requires platform-settings.project.create and .manage-components.
- Settings › Development › Projects.
- Create the system, and set its owning group.
- Add a component: name it, choose its type, and link it to the system.
- Check the Catalog — it should now appear with the right owner.
Hand a project to a different team
Requires platform-settings.project.assign-owner.
- Open the project and change the owner group.
- Check the components: they may carry their own ownership and not follow the system automatically.
Detach a component
Requires platform-settings.project.manage-components.
Unlinking does not delete the component. It stays, without a parent system — either link it elsewhere in the same sitting or delete it.
Scenario
A new service needs to appear in the catalog, owned by the right team.
- Confirm the owning group exists in People & Access › Groups. Create it if not.
- Settings › Development › Projects — if the service belongs to an existing project, skip to step 3; otherwise create the system and set its owner.
- Add the component. Choose the type that matches what it actually is; this is what makes catalog filters useful later.
- Link it to the system.
- Open the Catalog and confirm it appears with the correct owner.
- If the service has documentation, it now has somewhere to hang.
Doing step 1 last is the usual mistake: a component created before its group exists ends up unowned, and nobody notices until someone needs to ask a question about it.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| Component does not appear in the catalog | Not linked to a system, or the catalog has not refreshed | The components table | Link it to a system; wait for the next refresh |
| Component shows no owner | Its system has no owning group, or the component is unlinked | The owner column | Set the owner on the system, and link the component |
| Cannot change the owner | Needs platform-settings.project.assign-owner, separate from .update |
Access Explorer | Ask for a role granting it |
| Owner group missing from the picker | The group does not exist | Groups | Create it, then reopen the project |
| Deleted a system, components remain | Deleting a system does not delete its components | The components table | Relink or delete them explicitly |