# Manage address book contacts

Source: https://docs.settlemint.com/docs/operators/user-guides/user-management/manage-address-book-contacts
Review, edit, and delete address book contacts in the DALP dapp so transfer and operator workflows use the intended wallet address.



Address book contacts give DALP operators a named EVM wallet record for forms. Operators can reuse the saved wallet in minting, burning, transfers, and other workflows that accept a wallet address.

Open **Contacts**, select a saved record, and use the detail page to confirm the wallet before reusing the contact in an operator workflow. A contact is a convenience record for an EVM wallet address. The contact record does not verify the identity behind the wallet, grant permissions, or prove that the wallet can receive a regulated asset.

## Prerequisites [#prerequisites]

Before you edit or delete a contact, confirm:

* you are signed in to the correct organisation and network;
* the contact already exists in the address book;
* the replacement wallet, if you are changing it, is the intended EVM address for the recipient or operator record;
* any regulated transfer that uses the contact still passes the asset's identity, compliance, role, and balance checks.

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

1. Open **Contacts** from the dapp navigation.
2. Search or scan the list for the saved name or wallet.
3. Open the contact detail page.
4. Confirm the display name, wallet address, creation time, and last update time.
5. Copy the wallet address from the detail header or the basic information card when you compare the record with an external source.

Treat the displayed wallet as the value DALP submits when a later form uses that contact. If the name is correct but the wallet is wrong, edit the contact before submitting the transfer or operator action.

The detail page subscribes to the current contact record. If another operator updates the same address book entry, refresh the detail view before using the wallet in a regulated action.

## Add a contact [#add-a-contact]

1. Open **Contacts** from the dapp navigation.
2. Select **Add contact**.
3. Enter a display name.
4. Select or paste the EVM wallet address.
5. Save the contact.
6. Confirm the new contact appears in the contacts list or global search before you reuse it in another workflow.

DALP stores the contact as an address book record for the active organisation. The save action refreshes the contacts list and global search results after the request succeeds.

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

1. Open the contact detail page.
2. Select **Edit**.
3. Update the display name or wallet address.
4. Save the contact.
5. Reopen the address book list or the contact detail page and confirm the updated value.

DALP trims the contact name and requires a valid EVM wallet address. The save action refreshes contact list data, the contact detail record, and global search results so the updated contact is available to address pickers after the request succeeds.

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

1. Open the contact detail page.
2. Select **Delete**.
3. Read the confirmation message.
4. Confirm the delete action only when the contact is obsolete or unsafe to reuse.

After DALP accepts the delete request, the dapp refreshes contact and global search data and returns you to the contacts list.

Deleting an address book contact removes the convenience record. Deletion does not delete the wallet, cancel submitted transactions, remove token balances, change identity claims, or erase historical activity that already refers to the address.

## Operating notes [#operating-notes]

| Situation                               | What DALP shows                                                                                          | Operator action                                                                                          |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Contact cannot be found                 | The dapp returns to the contacts list instead of opening a missing record.                               | Search the list again. Create a new contact only when the address book still needs that wallet record.   |
| New contact does not appear in search   | The save request has not refreshed the contacts list or global search result yet.                        | Reopen **Contacts** or wait for the success toast before using the contact from another form.            |
| Save fails                              | The dapp shows an error message with a reference when one is available.                                  | Reopen **Edit**, check the name and wallet address, then retry only after confirming the intended value. |
| Delete fails                            | The contact remains in place and the dapp shows an error message with a reference when one is available. | Retry only after confirming the contact should still be removed.                                         |
| Contact was used in a prior transaction | The contact can still be edited or deleted as an address book record.                                    | Use transaction history, token events, and audit evidence to review the prior action.                    |

## Compliance scope [#compliance-scope]

An address book contact is not an identity record. Regulated asset workflows still rely on the asset's configured controls, such as trusted identity claims, allow lists, block lists, role permissions, and wallet verification. Do not treat a saved contact name as proof that the wallet belongs to a verified investor, issuer, administrator, custodian, or counterparty.

## Related pages [#related-pages]

* [Review address book contacts](/docs/operators/user-guides/asset-servicing/review-address-book-contact) for the contact detail page, copy action, edit sheet, and delete confirmation.
* [Address book contacts API](/docs/developers/developer-guides/api-integration/address-book-contacts) for API fields and error codes.
* [Identity and compliance](/docs/compliance-security/security/identity-compliance) for recipient verification requirements.
* [Asset detail workspace](/docs/operators/user-guides/asset-servicing/asset-detail-workspace) for operator actions that can use contacts in asset workflows.