Skip to main content

← Back to parent Epic

MAZENG-FT-16 · Change a collaborator's project role

Feature intent

A collaborator's responsibilities change and their project access must change without removing and re-adding them.

Why it matters

A collaborator's responsibilities change and their project access must change without removing and re-adding them.

Expected outcome

Keeps project authority aligned with current team responsibilities.

In scope

  • Allow an authorized owner or maintainer to select an existing project member.
  • Assign the selected member another supported project role.
  • Apply the changed role to subsequent project authorization decisions.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-4
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    An authorized role change is visible after refresh.

  2. 02

    The new role governs the collaborator's subsequent project actions without requiring membership recreation.

  3. 03

    An unauthorized or invalid attempt fails without changing the existing membership or role.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy API support exists, but the inspected member table does not clearly expose role editing; the Next Gen interaction requires refinement.
  • Owner transfer, last-owner protection, self-demotion, and administrator-versus-owner safeguards require explicit product semantics.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source