> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/users-management/instance-permission/contacts-permissions-how-to-assign-and-use.md).
# Contacts Permissions: How to Assign and Use
Contact permissions allow team members to access, manage, and organize contact-related data in Mercuri CX. By assigning these permissions, users can efficiently handle customer information, maintain updated contact records, and segment contacts for marketing or operational purposes.
***
### Steps to Assign Contacts Permission:
1. Navigate to **Settings** from the left sidebar.
2. Click on **Teams**.
3. Select an existing user or click **Add User** to create a new one.
4. Enter the required details such as **Name**, **Email**, and **Role**.
5. Click on the **Configure Permissions** button.
6. In the permissions window, go to the **Instance Permissions** tab.
7. Locate the **Contacts** section.
8. Enable or disable specific permissions based on the level of access you want to provide.
***
### Contacts Permissions Explained
Here’s a detailed explanation of each option under **Contacts** and its use case:
1. **View Contacts**
* Allows the team member to view the list of contacts synced from the connected platform (e.g., Shopify, Wix, Pipedrive).
* ***Use Case**:* Ideal for support agents or sales team members who need to reference customer details but should not make changes.
2. **Manage Contacts**
* Grants the ability to edit or update existing contact details such as name, email, or phone number.
* ***Use Case:*** Suitable for customer service or CRM managers responsible for keeping contact information accurate.
3. **Upload Contacts**
* Allows the user to bulk upload new contacts into the system using a CSV or Excel file.\
\&#xNAN;***Use Case:*** Useful for marketing teams adding new leads or customer lists from external sources.
4. **Download Contacts**
* Enables the team member to export and download contact data for reporting or analysis.
* ***Use Case:*** Helpful for analysts or managers preparing reports, performing audits, or integrating data with other tools.
5. **Manage Contact Labels**
* Allows the user to create, edit, or delete labels/tags that categorize contacts.
* ***Use Case:*** Best for marketing and sales teams to segment contacts for campaigns or personalized outreach.
6. **View Contact List**
* Gives access to view different contact lists (e.g., segmented customer lists or marketing lists).
* ***Use Case:*** Useful for team members who need to see the context of contact groupings without making changes.
7. **Manage Contact List**
* Allows the user to create new contact lists, edit existing ones, or delete outdated lists.
* ***Use Case:*** Ideal for campaign managers or admins responsible for organizing contacts into actionable lists.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.mercuri.cx/features/users-management/instance-permission/contacts-permissions-how-to-assign-and-use.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.