> ## Documentation Index > Fetch the complete documentation index at: https://support.vocal.solutions/llms.txt > Use this file to discover all available pages before exploring further. # Lead access and stopping contact > Who can work your leads, what duplicates mean, and how to stop follow-ups without deleting history. Recruiters see their assigned CRM leads and the personal lists they import. Another recruiter doesn't gain access to your CRM list just because you're in the same group. ## What can my manager see? Workspace **Owners** and **Admins** have CRM's **Team** tools and can review recruiters' leads. **View as** shows a recruiter's table read-only. The team's management tools handle assignments separately. A **group manager** isn't automatically a workspace Admin and doesn't gain the CRM Team tools from that responsibility alone. They may still have access to conversations on numbers they manage. [Groups](https://support.vocal.solutions/team/groups.md) explains that access. Calls, texts, recordings, and evidence keep their own access rules. Having access to a lead doesn't automatically make every conversation with the same driver readable. **Watch: review a recruiter's leads ยท 18 seconds** Using example data: an Owner or Admin opens **Team**, chooses **View as**, and opens a lead in the recruiter's read-only table. ## Can the same driver appear on more than one list? Yes, a driver can have separate list entries. **Also on**, when shown in the lead panel, helps identify other relevant lists. It isn't permission to open another recruiter's private notes or calls. Imports check for active assignments to avoid handing the same driver to two recruiters by accident. Only an Owner or Admin can deliberately override that duplicate check. See [Import leads](https://support.vocal.solutions/crm/importing-leads.md). Shared driver attributes can be reused between entries, while notes, status, and follow-up progress belong to a particular lead entry. Don't put confidential conversation notes into a shared driver attribute. ## Hand a lead to someone else Ask an Owner or Admin to use the CRM Team tools. Renaming a list, importing the number again, or sharing a phonebook contact isn't a lead reassignment. After a handoff, check the destination list, assignee, and next follow-up. Don't assume the receiving recruiter's plan or callback date will be identical. If the lead leaves your assignments, it may disappear from your CRM view. ## Stop contacting a lead Open **More actions** in the lead panel to stop follow-ups, mark a wrong number, or record a do-not-call request. The lead can also show restrictions or results recorded from its activity: | Action or state | Meaning | | - | - | | **Stop following up** | Stops the lead's follow-up work; keeps the record and activity | | **Wrong number** | Records that this isn't the right number and stops follow-up | | **Do not call** | Records a do-not-call restriction; CRM refuses calls and texts to that number | | **Opted out** | The person opted out of texts; CRM stops follow-up and refuses texts | | **Dead number** | The number was reported out of service and follow-up stops | Use **Do not call** when the person asks not to be called. **Stop following up** alone isn't the same restriction. A text opt-out is separate from a do-not-call request. Don't use another screen, number, or import to work around a person's request to stop contact. ## Can I resume later? **Resume following up** is available for a stopped lead unless the number is on the do-not-call list or opted out of texts. Read the next action it shows. **Restart plan** starts at step one instead. Neither action lifts do-not-call or text opt-out restrictions. A person who opted out of texts can text START to opt back in; don't change their status to pretend they did. Ask support if a restriction was recorded incorrectly. Stopping follow-ups doesn't delete notes, calls, or messages. [Import recovery](https://support.vocal.solutions/crm/importing-leads.md#rename-a-list-or-undo-an-import) only removes eligible untouched imports. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.