`MAZENG-FT-17` · Leave a project or remove a collaborator

Feature intent

A person needs to leave unwanted project work, while project managers need to remove access that is no longer appropriate.

Why it matters

A person needs to leave unwanted project work, while project managers need to remove access that is no longer appropriate.

Prevents stale access and lets users control their own project participation.

Allow a project member to leave a project when ownership safeguards permit it.
Allow an authorized owner or maintainer to remove another collaborator.
Refresh project-member and accessible-project lists after successful departure or removal.
Prevent the project from becoming orphaned when the last owner is involved.

Acceptance

01
A removed collaborator loses project access and disappears from the member list.
02
A person who leaves is returned to their remaining accessible projects and no longer sees the departed project as accessible.
03
An unauthorized removal attempt is rejected without changing membership.
04
The last-owner case is handled without orphaning the project or silently discarding ownership.

None recorded.

Legacy UI offers self-leave while the API route requires owner or maintainer authority, so an ordinary member's self-leave may fail; Next Gen must align the interaction and authorization contract.
Last-owner, owner-removal, ownership-transfer, and removal-of-self rules are absent and require explicit product decisions.

No authoritative Architecture tasks are linked.