> 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/assign-me-to-shipper.md).
# Assign Me To Shipper
Assign companies to help your team avoid reaching out to the same prospects.
### Overview
By assigning yourself to a shipper, you will let your team know that you will be or are already pursuing them as a prospect.
### From The Magic Map
Open a [Shipper Profile](/magic-map/shipper-profiles.md) card (illustrated below), and click the plus (+) button in the top left.
### From The CRM Company View
After you or someone in the same workspace as you has assigned themselves, go to the CRM page and switch to the Company Centric tab. Below the parent company details on the left, you will see an 'Assigned To' section, click the 'Assign To Me' button, or click the existing assignee to change who is assigned (only available to Owner roles).
Owner roles can override assigned to members by hovering over the existing assigned member from the Company Centric view
### Un-Assigning
### **From The CRM Company View**
Go to the CRM page and switch to the `Company Centric` tab in the CRM page. If you are assigned to a particular company (or an owner), you can hover over your name and click the `X` icon.
### From the MagicMap
Open a [Shipper Profile](/magic-map/shipper-profiles.md) card of a company which you're assigned to, click the (+) button at the top left, click the 'Unassign Me' button.
---
# 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.shippercrm.com/teams-and-agencies/assign-me-to-shipper.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.
