JE Shared Account Layer

One identity, many Jersey services.

Cleanje and Walkje should not become separate account silos. The safer route is a shared JE Account Passport: one user identity, separate service roles, separate product permissions, and VoidComms-style trust events underneath.

Shared username

Users can keep one JE username across Cleanje, Walkje and future services.

Safe first step: identity mapping.

Separate roles

A person can be a Cleanje customer, Cleanje provider, Walkje owner or Walkje walker without confusing permissions.

No dangerous cross-role leakage.

Trust passport

Completed jobs, proof events, disputes and admin decisions can feed one portable trust history later.

Do not merge payouts or private documents yet.

Correct build sequence

Phase 1: Create JE Account Passport page and mapping model.

Phase 2: Add API health route for shared-account readiness.

Phase 3: Add role model: cleanje_customer, cleanje_provider, walkje_owner, walkje_walker.

Phase 4: Add trust events: booking_created, proof_completed, dispute_opened, payout_released.

Phase 5: Later: connect Walkje and Cleanje through signed tokens, not shared raw passwords.

Open Cleanje Alpha Console Back to Cleanje