> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/lead-board-scoring/sales-users.md).
# Sales users
How to grant a user access to sales features so they can work on the lead board as part of a sales team.
A user in eMarketeer can have access to both marketing and sales features. With sales access, the user can work in a sales team on the lead board.
Managing users requires admin privileges.
Click the gear icon at the top right, choose Account Settings, and open Users & Teams to see the current users and their privileges.
## Create a new sales user
1. Click Create User. This opens the Create new user dialog.
2. Enter the email address of the new user.
3. Under Licenses, check Sales user — Access to Leads, then tick one or more sales teams the user should belong to. A user can belong to one or more sales teams. A sales user also gets access to CRM web panels by default, so **CRM Web Panels** under **Access** is checked automatically.
4. Click Create user and send login email.
The user is notified by email to set a password and complete the profile.
---
# 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://support.emarketeer.com/guides/lead-board-scoring/sales-users.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.
