Customer portal

Agreement

Review agreement state, dependencies and customer-safe evidence without exposing provider envelope data or private objects.

Signature lifecycle

Draft

Agreement is being prepared before a signature request is sent.

draft
  1. Draft

    Agreement is being prepared before a signature request is sent.

  2. Sent

    Signature request sent; completion waits for provider evidence.

  3. Viewed

    Agreement opened; signed status stays pending until evidence lands.

  4. Signed

    Signed evidence may still be pending Magnus application.

  5. Declined

    Customer declined the agreement; support can issue a replacement.

  6. Expired

    Signature window elapsed; staff must reissue the agreement.

Provider redirect returns stay pending until fake webhook replay or staff evidence applies the next lifecycle step. Signed finality still requires Magnus evidence and stored signed object proof.

Agreement

Pending evidence

Review the agreement pack and track what is still blocking completion. Signed status only becomes final after provider or staff evidence is processed.

SentFake lifecycle
Customer
Customer fixture
Site
Staff confirmation required
Booking
Move-in booking pending

Move-in gates

Dependencies before agreement finality

Pending Provider Or Manual Evidence

Signed evidence

Sent

Signed state waits for provider or manual evidence before move-in can continue.

Document dependency

Needs Review

Proof of address is required before staff can approve move-in.

Payment dependency

Pending Provider Confirmation

Payment browser returns are not final agreement evidence.

Evidence safety

Private agreement data stays hidden

Customer-safe view

Provider envelope ID

false

Signed object key

false

Private object data

false

If a signing provider returns the browser to Magnus, the customer still sees a pending state until the provider callback or staff record confirms signed evidence.