Skip to main content

← Back to parent Epic

MAZENG-FT-1 · Create a personal Maze account

Feature intent

A new user needs a personal identity in Maze rather than shared credentials.

Why it matters

A new user needs a personal identity in Maze rather than shared credentials.

Expected outcome

Enables attributable, self-service access to Maze.

In scope

  • Present and require acceptance of applicable policy terms.
  • Collect first name, last name, email address, password, and password confirmation.
  • Validate required fields, email format, password policy, password confirmation, and email uniqueness before account creation.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-1
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    Valid registration details create exactly one personal account and route the person to sign-in.

  2. 02

    Invalid email, an insufficient password, mismatched passwords, missing required fields, or an existing email is visibly rejected without creating an account.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Policy content and user-storage behavior must be defined and available.
  • The Next Gen password policy must be consistently enforced in both client and server; the legacy server enforced only minimum length despite defining a stronger unused rule.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source