> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/contacts/adding-new-contacts/bulk-upload-contacts.md).

# Adding access to bulk upload contacts

Any organization's admins can upload **NEW** contacts with the bulk upload tool. However, this tool can also be used by those with permission to **bulk update** existing contacts. Typically, bulk updating should be done by Platform Administrators, or well-trained super admins, to prevent overwriting information that should be kept. Here's how our Support team can give the latter access:

1. Create a separate role group such as "Access to Contacts Upload" and just add the admins who should have access and know how to use it properly.
2. While logged in to the tenant account, click on **Settings**, then **Actions**. Set filter for action url of **admin/contacts/people/upload/update** and open that action.
3. In the **Authorization** panel, add the group that should have permissions to bulk upload, and save.
4. Admins will need to log out and back in before permissions will be applied to their accounts.


---

# 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.shiftiq.com/help/contacts/adding-new-contacts/bulk-upload-contacts.md?ask=<question>&goal=<endgoal>
```

`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.