> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/administrator-settings/admin-settings/roles-and-permissions.md).

# Roles & Permissions

#### There are four user roles in emSigner. A brief explanation is as mentioned below:

**Super Admin** has full privilege to access the system and is capable of defining roles and granting access to Admins and Users in the system.

**Admin** has control over operations of a plan or even operations of an organization. An Admin can create workflows, departments, users & adhoc users. They can also provide access privileges to the users in a workflow management system for accessing different departmental workflows based on their Job Function / Role / Profile etc. Admin roles and access to all the modules will be defined by the Super Admin. 

**User** will be created by the Admin and required access shall be provided based on the requirement.

**Adhoc user** is one who is not a regular user of the organization nor is he working in the organization. He will be provided with login credentials which will be valid until the completion of signing the document. This account can be only used as a one time case.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.emsigner.com/administrator-settings/admin-settings/roles-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.