Source: https://docs.amadalis.ai/commerce/customer-identity/

# Customer accounts, email and claims

Checked against the product’s code on 7 November 2026.

Open **Commerce** > **[Customer identity](https://docs.amadalis.ai/reference/glossary/#customer-identity)**. These settings concern visitors and shoppers using your site’s account pages. They are separate from your team’s Praxis account and Admin roles.

Only an Admin can change these settings, connect customer email or act on [claims](https://docs.amadalis.ai/reference/glossary/#claim).

## Review registration and presentation

**Customer registration** controls whether visitors can create shopper accounts. Read settings taken from the site defaults and the current readiness state before enabling it. A registration setting does not grant a shopper a role on your site’s editing team.

Under **How your account pages look**:

1.  Choose the offered layout.
2.  Review the headings.
3.  Review the supporting words.
4.  Choose the privacy destination from the available links.
5.  Choose the terms destination from the available links.
6.  Choose **Review and save**.
7.  Read the proposed change.
8.  Save it through its confirmation.
9.  Read the result.

## Configure customer email

**Customer email** offers Resend or an [SMTP](https://docs.amadalis.ai/reference/glossary/#smtp) email server, sender and reply details, and **Send test to my administrator email**, which sends the test to your own address once the credentials are connected. Enter credentials only in this dedicated screen. Sender verification remains with the selected provider.

The platform’s default provider can already be selected. To connect your own sender in **Customer email**:

1.  Choose **Connect a provider (optional)**, or the replacement action for an existing connection.
2.  Choose **Resend** or **SMTP**.
3.  For Resend, enter **Resend API key**.
4.  For SMTP, enter **Public SMTP hostname**.
5.  For SMTP, choose **Secure submission**.
6.  For SMTP, enter **SMTP username**.
7.  For SMTP, enter **SMTP password**.
8.  Enter the authorised sender in **From**.
9.  Enter **Reply-To (optional)** if needed.
10.  Choose **Review test and connection**.
11.  Read the proposed test and connection.
12.  Confirm only the intended change.
13.  Read the resulting configuration.

For an additional test after connection:

1.  Choose **Send test to my administrator email**.
2.  Read its approval card.
3.  Confirm only the intended test.
4.  Read the result.
5.  Check your real test mailbox.

An Admin can also ask the copilot to update the supported registration settings, disconnect the current customer email connection, or send a test. Read each approval card. Connecting a provider and entering its credentials stay in **Customer email**.

Check the resulting configuration and a real test mailbox. A sender being saved does not guarantee that every future sign in or order email will arrive. Keep missing sender or failed send states visible during setup.

## Handle imported claims

**Claims** helps the right person take ownership of an imported account. It lists imported accounts that edited or ran your old site; ordinary customers claim their accounts themselves from the emailed link.

Approval activates the account so its owner can sign in, and it cannot be undone. Approve only people you still want to have an account. Imported identity is not permission to reuse an old password or payment credential.

1.  Open the intended imported account in **Claims**.
2.  Choose **Send the claim email**.
3.  Read its approval card.
4.  Confirm only the intended send.
5.  Wait for the person to confirm their address.
6.  Check the confirmation in the claim’s details.
7.  Choose **Approve**.
8.  Read that action’s approval card.
9.  Confirm only the intended activation.
10.  Read the result.

For an erasure request, use the separate [shopper account erasure](https://docs.amadalis.ai/privacy/visitor-data/) action in **Privacy & Data** > **Visitor Data**. Visitor erasure alone does not remove the shopper account. Review the subscription refusal and the checkout details that remain before confirming.

Use the customer’s supported verification path and inspect its outcome. For the shopper experience, read [Storefront and shopper accounts](https://docs.amadalis.ai/commerce/storefront-and-shopper/). For your own staff, read [Your team](https://docs.amadalis.ai/account/your-team/).