#Projects

A project is a named bundle of services. Engaging it fetches credentials for every member at once, at the same environment and mode.

If your work touches four accounts at a time, this is the difference between four engages and one.

#Creating a project

In the PROJECTS drawer, press + NEW PROJECT, name it, and tick the services that belong to it. Projects are scoped to one org.

Name it after the work, not the infrastructure — checkout-rewrite or incident-4471 beats core-plus-payments. The point is to have a button that matches the thing you are actually doing.

#Engaging a project

Press ENGAGE on the project card. Every member is engaged at the chosen environment and mode, and they appear in the rail grouped under the project name.

The card's button carries the same rules as a single service: it names the environment and mode, it is red for production, and ADMIN on PRD requires a press-and-hold.

#Partial failure is normal

One member failing never blocks the rest. If a service in the bundle has no role you can assume on that environment, the others still engage and the failure is reported per row. You get the working subset rather than an all-or-nothing error.

This matters more than it sounds: a project spanning six accounts where one has a permissions gap is still a project you can work in.

#Changing environment or mode

CHANGE ENV/MODE on the card reveals the selectors. The available choices are the union of what the members support, so a project containing a standalone account and a four-environment service offers everything both can do.

Your last choice per project is remembered, and the card shows it — 4 SERVICES · LAST PRD/READONLY — so you can see what a click will do before you make it.

#Editing membership

⚙ SETTINGS on the project card opens its membership list, where you can add or remove services. Changes save as you make them.

They take effect on the next engage; services already engaged from a previous run stay engaged until you disengage them.

Deleting the project lives at the bottom of the same panel — see Deleting a project below.

#Deleting a project

DELETE PROJECT… at the bottom of the settings panel. It asks once, then removes the project from the list.

Deleting is reversible. The project moves to RECENTLY DELETED at the bottom of the projects list, where ↩ RESTORE brings it back with its members intact. A project is a bundle you assembled by hand, so losing one to a misclick would cost real work to rebuild.

DELETE FOREVER in the recently-deleted list purges the archive entry. That one is permanent, and it is the only action here that actually loses anything.

Restoring refuses if you have since created a new project under the same name — an undo that silently replaced your current work with an older copy would be worse than no undo at all. Rename one of them first.

#Adding a service by dragging

A service you engaged on its own appears in the rail as its own block. Drag it onto a project's group to add it there — the moment you realise it belongs to that project is the moment it is easiest to say so.

The drop does two things: adds the service to the project's membership, so future engages of the project include it, and attaches the live engagement to the project, so it moves into that group immediately rather than after the next engage.

#Pinning

The ★ pins a project to the top of the list. Unpinned projects sort by how recently you engaged them, so the list stays roughly in the order you actually work — and the pin overrides that for the two or three you always want first.

#Disengaging a project

The disconnect icon on the project's group in the rail disengages every member in one action. DISENGAGE ALL clears everything, across all projects and ad-hoc engages.

Individual members can be disengaged on their own from inside the group, if you want to drop production access but keep the rest.

#Projects versus ad-hoc engages

A service engaged directly from the SERVICES drawer is an ad-hoc engage. It stands alone in the rail rather than joining a project group.

Both deliver identical credentials — the grouping is bookkeeping, so you can disengage a whole piece of work at once and see at a glance what is on.