> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/workflow-builder/workflow-builder-permissions.md).
# Workflow Builder Permissions
How to add the workflow builder permission to a role
Not all users will have access to the **Workflow Builder**. Any user who is an admin will by default have access. Users who are not an admin will need to have a role that has the `ReadEmbeddedWorkflowBuilder` permission. This permission is in the `EmbeddedWorkflowBuilder` permission group.
To add the `ReadEmbeddedWorkflowBuilder` permission to a role follow these steps:
Navigate to the Settings page in ION:
Click on Organization:
Click on Members:
Click on Roles:
Locate the Role that you want to add the permission to then click on the green up arrow next to the name of the role.
Click on the `EmbeddedWorkflowBuilder` checkbox to enable the permission for the role.
Repeat these steps to enable the permission for all applicable roles.
---
# 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://manual.firstresonance.io/workflow-builder/workflow-builder-permissions.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.
