> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/settings/default-people-and-companies-views.md).
# Default People & Companies Views
**Default Views** let you define what shows up when anyone in your workspace opens the **My Companies** or **My People** view. You can:
* Match records on **more than one owner field** (for example, a primary owner *and* a secondary/overlay owner)
* Add **any other filters** that should apply by default — the same filters available on the Companies and People pages
The settings apply to everyone in the workspace, and each user sees records matched against **their own email**.
### Where to find it
Go to **Workspace Settings → Default Views.** You'll see two sections:
| Section | Controls |
| ---------------- | ----------------------------------------------------- |
| **My Companies** | The default "My Companies" view on the Companies page |
| **My People** | The default "My People" view on the People page |
### How owner matching works
Under **Match my email in these owner fields**, select one or more fields that contain an owner's email address.
A record is included in a user's view when the **viewer's email appears in *****any***** of the selected fields** (OR logic)
### Tips
* **Configure each section separately.** My Companies and My People have their own owner fields, filters, and **Save team default** button.
* **Use email fields.** Owner matching compares against the viewer's login email, so pick fields that store owner **email addresses**, not names or IDs.
* **Keep defaults broad.** Default filters apply to everyone, so add only filters that make sense for the whole team.
---
# 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.hockeystack.com/marketing-intelligence/settings/default-people-and-companies-views.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.
