> For the complete documentation index, see [llms.txt](https://docs.shippercrm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shippercrm.com/teams-and-agencies/workspaces.md).

# Workspaces

Workspaces in Shipper CRM are useful for setting up an isolated environment for sales team(s) within (or outside) your organization. We encourage you to think about workspaces as having two distinct types:

1. Corporate workspaces
2. Agency workspaces

<figure><img src="/files/L5Fh5tSSKmHc80q2IzIt" alt=""><figcaption><p>The main corporate workspace is shown above followed by agencies (below).</p></figcaption></figure>

### Corporate workspaces

A corporate workspace is a workspace for all the W2 employees you have in your brokerage. If your brokerage operates under a single team model, then you should use one shared corporate workspace as your main workspace across your organization.

### Agency workspaces

An agency workspace is a workspace that has been created specifically for an agent or agency that is working directly under your brokerages authority. If your brokerage works with broker-agents or broker-agencies, you should setup a workspace for each agent / agency that you work with. If the agent / agency has sub-agents that they employee, those sub-agents should preside in that particular agency workspace.

#### Collision Avoidance

Shippers & contacts that are added in one agency workspace within your organization, will not be allowed to be added by a different agency, in an effort to prevent conflicts during outreach. This allows shippers to be kept separated between each agency. This separation of data is explained in more detail in the [assigning companies section](/teams-and-agencies/assign-me-to-shipper.md).


---

# 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.shippercrm.com/teams-and-agencies/workspaces.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.