# Review address book contacts

Source: https://docs.settlemint.com/docs/user-guides/asset-servicing/review-address-book-contact
Open a saved contact in DALP, confirm its wallet address and timestamps, then edit or delete the contact when the local address book entry is wrong.



Address book contacts store wallet labels for reuse in the DALP dapp. Review a saved contact before selecting it for a regulated asset operation. The contact detail page helps you verify the address book entry. The detail page does not change the compliance checks that run when you submit an asset transaction.

<Mermaid
  chart="graph TD
    A[Open Contacts] --> B[Select a saved contact]
    B --> C[Review name, wallet address, created time, and updated time]
    C --> D{Is the entry correct?}
    D -->|Yes| E[Copy the wallet address for the next workflow]
    D -->|No| F[Edit the contact or delete the entry]
    E --> G[Run the asset operation's identity, compliance, role, and approval checks]
    F --> H[Confirm Contacts and global search refresh]"
/>

The diagram shows the address book review path only. A copied contact address still has to pass the checks required by the asset operation that uses it.

## Before you start [#before-you-start]

You need:

* access to **Contacts** in the dapp
* a saved contact in the active environment
* permission to edit or delete contacts if you need to change the entry

Contacts are convenience records owned by the signed-in operator. The asset operation still enforces identity, compliance, freeze, approval, and role checks when you submit the transaction.

## Review a contact [#review-a-contact]

1. Open **Contacts**.
2. Select the contact you want to review.
3. Check the contact name and wallet address on the detail page.
4. Use the copy action beside the wallet address if you need to paste it into another workflow.
5. Review the created and updated timestamps when you need to confirm whether the entry was recently changed.

The detail page reads the saved contact by its contact ID. If DALP cannot read the selected contact during the initial route load, it returns you to the Contacts list.

## What you can confirm [#what-you-can-confirm]

The basic information card shows the fields that matter before reuse:

| Field          | What to check                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------ |
| Name           | Confirm the label matches the counterparty or internal recipient you expect.                     |
| Wallet address | Confirm the full address before copying it into a transfer, mint, burn, or role-change workflow. |
| Created at     | Use this timestamp to understand when the contact was first saved.                               |
| Updated at     | Use this timestamp to see whether the contact changed recently.                                  |

A contact is not proof that the address can receive a regulated asset. Before you submit an asset operation, verify the recipient, role, identity, compliance, and approval requirements in that operation.

## Edit a contact [#edit-a-contact]

Use **Edit** from the basic information card when the saved name or wallet address needs to change. The edit sheet opens on the contact detail page with the current name and wallet address filled in.

1. Change the contact name or wallet address.
2. Save the form.
3. Confirm the detail page shows the updated value before reusing the contact.

DALP refreshes the contact detail, Contacts list, and global search results after the save succeeds.

## Delete a contact [#delete-a-contact]

Use **Delete** only when the contact should no longer be reused from the address book. DALP asks you to confirm the deletion before removing the entry.

Deleting a contact removes the address book entry, refreshes Contacts and global search results, and returns you to the Contacts list. Contact deletion does not affect token balances, identities, claims, transfer approvals, custody rules, or historic transaction evidence.

## Related guides [#related-guides]

* [Address book contacts API](/docs/developer-guides/api-integration/address-book-contacts) for the contact data model, API calls, and dapp behavior behind saved contacts
* [DALP CLI command reference](/docs/developer-guides/cli/command-reference#contact-commands) for scripted contact list, upsert, and delete workflows
* [Token holders and transfers](/docs/developer-guides/api-integration/token-holders-transfers) for the regulated transfer checks that still apply after you copy a contact address
* [Asset detail workspace](/docs/user-guides/asset-servicing/asset-detail-workspace) for reviewing asset state before running an operation