> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-customers/customers/adding-managing-contacts.md).
# Adding (managing) contacts
Add, edit, or delete a contact (end user) under a customer account, and learn the entitlement states and ABL access rights a contact can have.
To add a new **contact (end-user)** to a "customer" account, navigate to the customer and select it in the "customers" section of the left-hand navigation.
* [Create a "customer"](/zentitle2-docs/ui-customers/customers.md) or select an existing one.
{% hint style="info" %}
Contacts can have several entitlement "states" and access rights to your software or the EUP:
* States for a contact (end-user):
* No rights but is an analytics user (e.g., Zengain user)
* No rights but is simply a "prospect" on the platform
* Has rights via a license key/code alone
* Has rights via ABL to software on the platform (but not the EUP)
* Has rights to software as well as access to the End User Portal (EUP) - needs to be an ABL user for EUP access
**ABL refers to a method of licensing contacts referred to as "ABL" on a tab within the menu.** ABL access is either by "**password**" (for Zentitle2 internal Account Based Licensing option) or "**Open ID Token**" (for the Open ID Connect option with your chosen iDP).
ABL users will get a login rather than just using a license key to access your software. It's a username/password approach rather than a license key approach.
**Contacts don't require ABL to access their entitlements. They can be given a license key/code instead, etc.**
ABL is part of every Z2 edition (Note: EUP is an option in our higher tiers).
{% endhint %}
### Adding contacts (to a customer)
* Click the "contacts" tab under an existing customer in the system.
* Click the "add" button on the top right of the page.
* Add a customer contact and their details. **The only mandatory field is the "email" address.**
{% hint style="info" %}
LinkedIn must be in the format: [https://www.linkedin.com/in/username](https://www.linkedin.com/in/username\)). For more details on the fields in use, [go here](/zentitle2-docs/ui-customers/customers/adding-managing-customers/the-customer-page/fields-explained.md).
{% endhint %}
When adding a phone number, select the country from the drop-down options, and the system will validate its structure for accuracy.
If you would like to make the contact a "key contact" for focus in the UI (with a star), choose that option from the drop-down box, or leave as is, the default is no for key contact.
* Click save when done.
#### Once the contact is added, you can add them to an entitlement
* Once added, you can [allocate an entitlement ](/zentitle2-docs/ui-entitlements/using-entitlements.md)to a contact
***
### Editing a user
* As before, navigate to the contacts tab for a customer.
* Find the contact to edit from the list and click that line item.
* Click the "edit" button on the contact.
* Edit the details as required.
* Add a location if you wish.
{% hint style="info" %}
Adding location data. Note the extra Country field, with state (if US), where you can manually add a location for territory filtering. The system may have already collected this.
{% endhint %}
* Click save.
***
### Deleting a user
* As before, navigate to the contacts tab for a customer.
* Find the contact to edit from the list and click that line item.
* Click the ellipsis on the right of the details.
* Click "delete contact."
* If the contact doesn't have any entitlements, it will be deleted; however, if entitlements are attached, it will undergo a further layer of security, as below.
{% hint style="success" %}
An additional layer of "security" has been added to ensure the user understands the consequences and has to take various actions before deleting the object.
{% endhint %}
* Click the radio buttons confirming this action and enter the confirmation text.
* Then click delete again to remove the contact.
{% hint style="danger" %}
Any form of deletion **CAN NOT BE UNDONE. BE VERY CAREFUL WHEN DELETING.**
{% endhint %}
### **Removing ABL from a contact**
Contacts can have ABL rights or not. These two states can be moved back and forth.
We have shown how to add rights to a contact; below, you can see how to easily remove the ABL rights.
* Edit a contact (as above) and review the ABL credentials in the right-hand box.
* In the top right are the three dots you can click. Click those.
* To remove the ABL access, "delete" the credentials, and that will remove them.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nalpeiron.com/zentitle2-docs/ui-customers/customers/adding-managing-contacts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
