> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/permission-sets-overview.md).
# Permission Sets
The Limio for Salesforce package offers four permission sets:
1. **Assisted Sales - Admin**
2. **Assisted Sales - User**
3. **Assisted Sales - Dev** (internal use only)
4. **Manage Configuration Objects in LFS** (internal use only)
This article focuses on the main features and permissions of the **Assisted Sales - Admin** and **Assisted Sales - User** permission sets.
### 1. Assisted Sales - Admin permission set
The **Assisted Sales - Admin** permission set is designed for users with administrative responsibilities, such as Sales Ops, Revenue Ops or Salesforce Administrators. It has the highest level of access which manifests in edit access to configuration records.
It allows access to Limio Console Application which includes the following tools and tabs:
*Note:* Limio Configs and Log Viewer Page tabs are for internal use only.
The **Assisted Sales - Admin** permission set includes a custom permission. It enables users to override blocked product rules during the Acquisition flow. For more information, visit [Dismiss Blocked Product Rule](/salesforce/setting-up/detailed-salesforce-setup/permission-sets-overview/dismiss-blocked-product.md).
### 2. Assisted Sales - User
The **Assisted Sales - User** permission set is designed to give users the ability to interact with Limio Flows and reading the app configuration, while not being able to update it. Users can access the Limio Console application.
Here is an example of a filtering rule view for a user with this permission set assigned, fields and Save buttons are read-only:
---
# 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.limio.com/salesforce/setting-up/detailed-salesforce-setup/permission-sets-overview.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)