> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/domain-settings.md).
# General & Domains
Zero needs to know which email domains are yours, or it will treat your own colleagues as prospects. The domain list is that answer, and it does two jobs:
* **Auto-contact creation** skips anyone at one of your domains, so your team and your outreach inboxes never become contact records.
* **Internal classification** decides which emails and meeting attendees count as internal. Your listed domains, your workspace's primary domain and the email domains of workspace members all count (generic providers like gmail.com do not). This feeds email labeling, meeting prep, and keeping your own company out of agent results.
## Set up
1. Go to **Settings → Workspace → General** (admin only).
2. Scroll to **Domains**.
3. Click **Add domain** and enter it, for example `zero.inc`. Pasting a full URL works — Zero keeps the domain.
4. Repeat for every domain you use, outreach domains included, and list subdomains separately if you send from them.
Changes save as you go. The trash button (**Remove domain**) takes one off the list.
---
# 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.zero.inc/settings/domain-settings.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.
