> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/users/assign-seats-and-licenses-to-new-users.md).

# Assigning Seats and Licenses

Before setting up any user access in Welkin, you need to assign a Welkin license to the user.

To assign a seat and license to a user:

* Log into Admin
* Click on 'Users' in the left vertical menu
* Click 'Send Invite' or 'Copy User'
* Fill in the user information
* In the 'License Seat' section, select a Welkin product from the dropdown
* If using a custom pricing plan, you may need to select a custom tier
* Click 'Send Invite' or 'Copy User'

The user will now be able to access the Welkin system. You can then configure the user's access permissions as needed.

**Note:** Welkin licenses may be limited based on your agreement with Welkin Health. Check with your Welkin account team to verify how many licenses you have available.


---

# 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.welkinhealth.com/admin/users/assign-seats-and-licenses-to-new-users.md?ask=<question>&goal=<user_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.