Organization danger zone: transfer ownership and delete

Open
  • Is something wrong?
#255 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
authentication, full-stack, security

Research direction

Start at Organization → Danger zone in the web UI and trace the existing unavailable buttons into the control-plane handlers. Read architecture rule 7 before implementing transfer or deletion, then identify where organization actions are audited and where enrolled servers are tracked. Done means transfer requires another admin, deletion requires typed-name confirmation and re-authentication and fails while servers remain enrolled, and both actions are audited.

Written by the indexing model from the issue text.

Description

priority:P2 security-review task track:control-plane track:web
Track

C: control plane, W: web UI

Scope
  • Transfer ownership to another admin, and delete an organization with typed-name confirmation and a re-authentication (architecture rule 7).
  • Buttons exist in Organization → Danger zone and say "not available yet".
Acceptance criteria

Deletion requires the confirmation token and fails if servers are still enrolled; both actions are audited.

Depends on

—

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.