> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/get-started/assign-licenses-and-permissions.md).

# Assign Licenses and Permissions

Use this flow after installing Flexi Kanban.

The order depends on your Salesforce org type:

* **Production and Developer orgs**: assign the managed package license first, then assign a permission set.
* **Sandbox orgs**: skip license assignment and assign the permission set directly.

{% hint style="info" %}
In Sandbox orgs, Salesforce creates an unlimited org-wide package license automatically.

You do not need to assign package licenses manually.
{% endhint %}

### Choose the right permission set

Assign only one permission set per user:

* **Flexi Kanban Admin** — full access to create and manage boards
* **Flexi Kanban User** — access to owned and shared boards
* **Flexi Kanban Viewer** — read-only access to shared boards

### Production and Developer orgs

In Production and Developer orgs, complete these steps in order.

{% stepper %}
{% step %}

### Step 1: Assign the managed package license

1. Open **Setup**.
2. Enter **Installed Packages** in Quick Find.
3. Select **Installed Packages**.
4. Find **Flexi Kanban**.
5. Click **Manage Licenses**.
6. Click **Add Users**.
7. Select the users who need access.
8. Save your changes.\
   \
   ![](https://3097383375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK2dgObBO5ydOH2ZXDJLa%2Fuploads%2Fw1Md9qTe7XmUTEjX2UEU%2Fimage.png?alt=media\&token=9f3f3189-0f5f-44c0-83ca-e8eb6cc4eba8)

If all licenses are already assigned, remove unused licenses or contact <sales@flexikanban.com> for more seats.
{% endstep %}

{% step %}

### Step 2: Assign a permission set

1. Open **Setup**.
2. Enter **Users** in Quick Find.
3. Select **Users**.
4. Open the user record.
5. In **Permission Set Assignments**, click **Edit Assignments**.
6. Add one of these permission sets:
   * **Flexi Kanban Admin**
   * **Flexi Kanban User**
   * **Flexi Kanban Viewer**
7. Save your changes.\
   \
   ![](https://3097383375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK2dgObBO5ydOH2ZXDJLa%2Fuploads%2FhYIqMfJxq2K5UE54Ymx9%2Fimage.png?alt=media\&token=cd400695-945a-4d35-8b2e-2bd2adfdb71f)

Do this only after the package license is assigned.
{% endstep %}
{% endstepper %}

### Sandbox orgs

In Sandbox orgs, assign only the permission set.

1. Open **Setup**.
2. Enter **Users** in Quick Find.
3. Select **Users**.
4. Open the user record.
5. In **Permission Set Assignments**, click **Edit Assignments**.
6. Add one of these permission sets:
   * **Flexi Kanban Admin**
   * **Flexi Kanban User**
   * **Flexi Kanban Viewer**
7. Save your changes.\
   \
   ![](https://3097383375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK2dgObBO5ydOH2ZXDJLa%2Fuploads%2FnswfuPUxDRHlX0c1ahns%2Fimage.png?alt=media\&token=09c31287-c314-43ac-b75b-10153572e50c)

No manual package license assignment is required in Sandbox.

### Quick summary

* **Sandbox**: assign the permission set only.
* **Production**: assign the managed package license first, then the permission set.
* **Developer org**: assign the managed package license first, then the permission set.


---

# 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.flexikanban.ai/get-started/assign-licenses-and-permissions.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.
