Leaving PackageMaze

The three self-serve exits take effect as you confirm them. Nothing is queued for a nightly job, and there is no cool-down you have to wait out.

The installation is GitHub's grant, so GitHub is where it ends. Each linked GitHub organization on your Organization settings screen carries a Manage on GitHub link to its installation, and PackageMaze learns about the uninstall from GitHub.

PackageMaze immediately loses repository access. Repository scans stop, new Projects stop being discovered, CI configuration is no longer read, and the Check Run that attributes a publish back to its commit stops being delivered.

What it deliberately does not do: uninstalling revokes nothing inside PackageMaze. Feeds keep serving, packages keep resolving, and every Token, Agent grant, and membership keeps working — package delivery must not depend on a version-control integration. A CI publish authorized by a CI access rule still succeeds; it just arrives without the Check Run. If your goal is to cut off access, use the sections below.

The GitHub organization stays listed under Organization settings, marked Uninstalled, until an Organization Admin chooses Dismiss. Dismiss hides the uninstalled row from the settings list. It does not delete the connection record, any Projects or recorded publish attribution, or state in GitHub. PackageMaze keeps the connection record because the Projects and publish attribution already recorded point back at it. Installing again later is a new grant. When PackageMaze next sees the connection active, the row becomes visible again and scanning resumes.

Organization → People → the member's row → Remove member. Only an Organization Admin can do it, and PackageMaze asks you to re-authenticate first.

Removal is one operation, and it closes every door at once:

• Every Token they own in this Organization is revoked — the ones they created themselves and the ones owned by their Agents.
• Every Agent grant they hold in this Organization is revoked, which closes that Agent's connection here.
• Any Agent change still waiting for approval in this Organization is cancelled.
• Their membership ends.

Two guardrails will stop you, so plan a departure around them. You cannot remove yourself — another Organization Admin has to do it — and you cannot remove the last Organization Admin, so promote someone before the only Admin leaves.

Removal is scoped to one Organization. Their PackageMaze account, their Agents, and their access to other Organizations are untouched. Their revoked Tokens and grants stay as revoked records so Usage history still resolves to a person, and the removal appears under Recent access changes.

You manage your own credentials in Account settings, under Tokens and Agents. An Organization Admin governs the ones that reach their Organization from Organization → People → the member's credentials. Either way, PackageMaze asks you to re-authenticate first.

Three scopes, deliberately separate, so you can cut exactly as much as you mean to:

• Revoke a Token. That one credential stops working. PackageMaze does not create or reveal a replacement Secret.
• Revoke an Agent's Organization grant. The Agent loses access to that one Organization and its connection there is closed. The Agent itself, and its access to your other Organizations, carry on unchanged.
• Revoke the Agent. Terminal. Every Organization grant, every connection, and every Token that Agent owns are revoked together.

Revocation is one-way. There is no un-revoke, and a revoked credential can never be reactivated — you issue a new Token, or reconnect the Agent and consent again.

An Organization Admin can revoke or narrow access to their Organization, but never receives someone else's replacement Secret. When an Admin requires a rotation instead of revoking, the current Secret stops working immediately and only the owner can set and see the new one.

There is no self-serve Organization deletion yet. Email [email protected] and PackageMaze will confirm what is removed before anything is deleted.

What you can do yourself, today, closes every access path into the Organization:

• Revoke the Tokens on each Feed's Tokens screen.
• Revoke each member's Agent grants and Tokens from Organization → People.
• Remove the members. PackageMaze requires one Organization Admin to remain.
• Uninstall the GitHub App from your GitHub organization.

After that, nothing can install from or publish to the Organization's Feeds. What is left is stored data and history, which is what the deletion request handles.

Revocation ends a credential's authority. It does not erase the evidence of what that credential did, because deleting the credential would leave your delivery and Build history pointing at nothing.

• Revoked Tokens, Agents, and grants are kept as revoked records rather than deleted, so past activity still names them. They cannot be reactivated.
• Recent access changes — what was created, narrowed, rotated, or revoked, by whom, and when — are kept for 365 days.
• Expired and revoked Agent connection credentials are deleted 30 days after they end.
• An uninstalled GitHub App installation is kept so publish attribution recorded through it still resolves, even if an Organization Admin dismisses its row from settings.

None of these records contain a Token Secret or an Agent's connection credentials. PackageMaze cannot show you a Secret after revocation because it never stored one.