Connect customer sign-in and reservation management

Public forms reduce first-contact friction. A customer account gives a returning customer a place to review and change their work. Laney uses the organization's connected platform accounts. It does not add a separate form-only account system.

What a customer can do

A signed-in customer can use /account on the organization landing site to:

• review their reservation time, organization or branch, notes, and status;
• cancel a pending or confirmed reservation;
• change a pending or confirmed reservation when an active change form exists;
• continue a form draft;
• review the form name, submission time, status, and answer summary.

The account reads only records owned by that customer inside the organization tree. Changing an address value or moving to another tenant domain does not reveal another customer's data.

Distinguish sign-in from messaging

Only a connected account with a sign-in capability appears on the customer login page.

A Kakao channel, LINE messaging account, or WhatsApp account is not automatically a sign-in provider. Connect the sign-in variant and check that its status is Connected.

1. Prepare a provider

1. Open Accounts.
2. Connect a Kakao, LINE, or Meta sign-in account to the correct organization or branch.
3. Register the exact callback or redirect URI in the provider console.
4. Request only the profile consent fields required by the organization.
5. Check that the connection is Connected.
6. Open /login on the real tenant landing domain.

If no provider is connected, the login page states that no sign-in providers are configured. Public forms can still work, but do not advertise customer account access.

Never put provider secrets in a Form Prompt, field Description, public link, support report, or screen recording.

2. Test identity and tenant scope

1. Sign in with a synthetic provider test account.
2. Check that the flow returns to /account.
3. Check the organization name and linked customer name or email.
4. Open the same account path on another tenant domain. Check that no other-tenant record appears.
5. Sign out. Open /account. Check that it returns to sign-in.

When an anonymous visitor signs in after starting a public form or AI conversation, Laney upgrades the current visitor session. It does not discard the current work and create an unrelated identity.

3. Prepare a reservation change form

The Change action appears only when the reservation organization has an active change form.

1. Create a reservation-target form in Forms.
2. Set Mode to Update Target.
3. Check that Access is fixed to Token.
4. Add only the basic and public custom fields that the form allows customers to change.
5. Activate the form. Test it with a synthetic pending or confirmed reservation.

Laney creates a secure link fixed to the signed-in customer and selected reservation. The customer does not enter or copy a reservation ID. Keep one primary active change form for each organization.

4. Check allowed actions

Cancel changes only the selected reservation. It does not cancel a separate companion reservation that happens to use the same time.

5. Check drafts and final responses

A draft from a named form appears with Continue form. This action restores the unsubmitted values through a new customer-bound resume path. A submitted response is read-only. Start a new form or use a reservation change form for a new action.

6. Compare customer and admin views

If a customer sees another person's record or a change action opens the wrong reservation, deactivate the change form. Record the organization, time, and synthetic reproduction steps. Do not copy customer data or a complete secure link into a support report.

See Choose public or secure form access for the complete link rules.

Check the result

• Only Connected login providers appear on the tenant login page.
• The signed-in customer sees only owned reservations, drafts, and responses.
• Only a pending or confirmed reservation allows cancellation.
• Change appears only when an active Update Target form exists.
• A draft can continue. A submitted response remains read-only.