> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/app-builder-amas/2024-app-builder-amas/nov-27-2024-workflow-management-in-app-builder-plus-permissions-and-role-based-access.md).
# Nov 27, 2024: Workflow management in App Builder, plus permissions and role-based access
### **Join live!**
Join us live biweekly on Wednesdays at 1:30 pm EST! Download the calendar invite below.
{% file src="/files/wWxd5Fby40Ps3x20LdsB" %}
## App Builder AMA video recording
{% embed url="" %}
### Contents of the recording:
π οΈ Updates: Forms permissions beta in action π; new portal enhancements are on the way!
π Discussed cloning & syncing apps in test/production, tackling challenges, and the future of Crate Marketplace.
π Key Q1 2025 goals: Syncing custom components + setting priorities for the road ahead.
π Chris showcased a workflow app with smart folder management, sub-workflows, and real-time syncing.
π Deep dive: Permissions + role-based access insights.
β Wrapped up with Q\&A
HOW TO GET HELP:
* π¬ Chat (Discord): [https://discord.gg/rewstββ](https://discord.gg/rewst%E2%80%8B%E2%80%8B)
* Private #{{ msp }} channel
* \#the-kewp
* π« Submit Tickets to:
* π Feature Request + Integration Requests:
**CLUCK UNIVERSITY β REWST TRAINING:**
* π¨βπ« Live Instructor-Led Training:
* π Rewst Foundations Training:
* βΆοΈ On-demand Videos:
**DOCS:**
* π₯ Rewst Docs:
* β©οΈ Jinja Docs:
* βοΈ App Builder Docs:
**KEY LINKS:**
* π Feature Request + Integration Requests:
---
# 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.rewst.help/updates/app-builder-amas/2024-app-builder-amas/nov-27-2024-workflow-management-in-app-builder-plus-permissions-and-role-based-access.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.