> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/platform/request-inbox.md). # Request Inbox The Request Inbox is your centralised hub for managing all human-in-the-loop tasks created by your workflows. It provides a unified interface to view, action, reassign, and track the history of all approval requests and input forms assigned to you or your team. ### Overview When workflows reach human-in-the-loop actions like Request Approval or Request Input, they create requests that appear in the Request Inbox. This ensures that critical human decisions and data collection don't get lost while maintaining workflow efficiency. ### Key Features * **Centralised Task Management**: All human-in-the-loop requests in one location * **Reassignment**: Hand a request to a different person or role * **Notes and Mentions**: Discuss a request's linked record with your team * **Inline Feedback**: Rate AI-generated content directly inside a request * **Notifications**: In-app and email alerts for new and reassigned requests * **Complete Audit Trail**: Track all decisions, submissions, and reassignments * **Powerful Filtering and Saved Views**: Organise requests your way * **Real-time Updates**: Workflow continuation upon request completion ### How to Access the Request Inbox **How to open your Request Inbox** 1. Navigate to the main Lleverage interface 2. Look for the "Requests" tab in your navigation menu 3. Click on the "Requests" tab to open your inbox 4. The inbox displays all requests assigned to you > πŸ’‘ **Tip**: You can also access the Request Inbox directly from email notification links for faster task completion. ### Understanding the Request Inbox Interface #### Inbox Tabs The tabs at the top of the inbox split your requests by type: * **All**: Every request visible to you * **Approvals**: Decision requests only * **Inputs**: Input form requests only * **Mentions**: Requests where someone has mentioned you in a note Any saved views you create appear as extra tabs after these. #### Request Statuses * **Open**: Waiting for someone to action it * **Completed**: Actioned β€” for approvals, the status shows the decision that was made (for example "Approved" or "Rejected"), along with any reason given * **Cancelled**: The request was cancelled * **Superseded**: A newer request for the same step replaced this one * **Failed**: The workflow behind the request hit an error (see Failed Requests below) ### How to Filter Requests Click the **Filter** button to open the filter menu. Active filters appear as chips. * **Assignee**: Filter by people or roles. By default you see requests for you and your role β€” clear this filter to see every request in the project (Builders and Owners only) * **Workflow**: Show requests from specific workflows * **Record**: Show requests linked to data table records β€” either a specific record, or any record matching a property value * **Status**: Attention Required, Completed, Cancelled, Superseded, or Failed * **Date Range**: Last 24 hours, Last 7 days, Last 30 days, or a custom range * **Created By**: Who triggered the request * **Type**: Decision or Input * **My Status**: Requests where you were Mentioned, or have Replied * **Hide Completed / Hide Responded**: On by default, to keep your inbox focused * **Show Archived**: Include archived requests > πŸ’‘ **Best Practice**: Use the Record filter to see every request that touches a particular record β€” for example, all requests for one supplier or one invoice. #### Saved Views 1. Apply your desired combination of filters 2. Click the "Save filter" button in the filter bar 3. Your saved view appears as a new tab 4. Right-click a saved view tab and choose "Set as default landing view" to make it the tab that opens first β€” it's marked with a small house icon ### How to Action Requests #### For Approval Requests **How to complete approval requests** 1. Click on an open approval request to open it 2. Review the provided information: * Title and description from the workflow * Any context or data from previous workflow steps * Available action buttons with different styling 3. Click the appropriate button to make your decision 4. The request status updates immediately 5. The workflow continues based on your selection > ⚠️ **Important**: Once you click an approval button, the action cannot be undone. Review all information carefully before making your decision. #### For Input Requests **How to complete input requests** 1. Click on an open input request to open it 2. Review the request description and context 3. Fill out all required form fields (marked as mandatory) 4. Complete optional fields if applicable 5. Click "Submit" to complete the request 6. The workflow continues with your provided data > πŸ’‘ **Form Completion Tip**: Required fields are clearly marked and must be completed before submission. Save time by gathering all necessary information before starting the form. > ⚠️ **Read-only requests**: Builders and Owners can view every request in the project, but a request can only be submitted by someone assigned to it. Requests you aren't assigned to open in read-only mode. ### How to Reassign a Request Requests can be handed to a different person or role β€” useful for holiday cover, workload balancing, or escalation. **How to reassign a request** 1. Open the request 2. Click the assignee avatars at the top of the request, then choose "Edit Assignee" 3. Tick the people who should be assigned (at least one is required) 4. Click "Save" You can also click the pencil icon on the "Requested input from…" bar inside the request, which additionally lets you assign to a whole role (Owner, Builder, Operator, or Member) instead of specific people. After reassigning: * Newly assigned people receive an in-app notification and an email * The reassignment is recorded in the request's history, showing who reassigned it and to whom > πŸ’‘ **Who can reassign**: Reassignment is available to Builders and Owners, and only on open or failed requests. ### How to Add Notes When a request is linked to a data table record, you can discuss it with your team using notes on that record. **How to add a note** 1. Open the request 2. Open the linked record β€” click the record chip above the request, or find it under "Records" in the request sidebar 3. Go to the "Comments" tab 4. Click "Add note", write your note, and submit Notes support **@ mentions** β€” type @ to mention a teammate: * Mentioned teammates get a notification, and the request appears in their **Mentions** tab * Other assignees are notified of new notes too * Notes on a record are visible to everyone in the project, across every request that touches that record * You can edit or delete your own notes > πŸ’‘ **Tip**: Use the "My Status" filter to find requests where you've been mentioned or have replied. ### How to Give Feedback You can rate AI-generated content directly inside a request, helping builders improve the workflow. **How to give feedback** 1. Hover over an AI-generated element inside the request 2. Click thumbs up ("Good response"), thumbs down ("Bad response"), or the comment icon for general feedback 3. Add an explanation in the text box 4. Click "Submit" You can also select a specific piece of text inside the element first β€” the feedback popover lets you attach your comment to exactly that part of the response. Feedback lands in the workflow's Feedback panel in the builder, where builders can review it, mark it resolved, and use it to improve the workflow. > πŸ’‘ **Why it matters**: Concrete feedback on real requests is the fastest way to make the automation better for everyone. ### Failed Requests If the workflow behind a request hits an error, the request is marked **Failed** and shows a banner explaining what went wrong. * Failed requests stay actionable: submit it again to retry the workflow from that step * Or archive the request to clear it from the queue * Failed requests can still be reassigned ### How to Re-open a Completed Request If a flow needs to be rewound β€” for example, a decision was made with the wrong information β€” a completed request can be re-opened. 1. Open the completed request 2. Open the request's menu and choose "Re-open Request" 3. A fresh open request is created for the same step, keeping the original assignees and details 4. Answering it again resumes the flow from this step > ⚠️ **Important**: Re-opening supersedes any other requests that were still open later in the same session β€” they'll show as "Superseded". ### Archiving Requests Use **Archive Request** in the request's menu to clear a request from the queue without actioning it. Archived requests show who archived them and when, can be brought back with "Unarchive", and can be found again using the "Show Archived" filter. ### The Request Sidebar Open the sidebar from the "Request" button on an open request to see: * **Records**: Data table records linked to this request * **Attachments**: Files attached to the request * **History**: The full timeline β€” creation, steps that ran, reassignments, submission, and archiving, each with who did it and when > πŸ’‘ **Compliance Benefit**: The history gives you a complete audit trail for every request, which helps with compliance requirements and troubleshooting. ### Notifications and Alerts #### Email Notifications You receive an email when: * A new request is assigned to you * A request is reassigned to or away from you Each email includes the request details and a "View Request" button that takes you straight to it. Depending on your notification preferences, emails arrive immediately or as a digest. #### In-Platform Notifications * **Badge Indicators**: The Requests tab shows your pending request count * **Assignment Alerts**: "New request assigned to you" notifications with a direct link * **Mention Alerts**: Notifications when someone mentions you in a note * **Real-time Updates**: New requests appear immediately, and completed ones update instantly > πŸ’‘ **Stay Connected**: Check your notification settings to ensure you don't miss critical approval requests or time-sensitive input needs. ### Getting Help Need help while working through requests? Click the **"Chat with us"** bubble in the sidebar to open the support chat: * Ask anything about Lleverage β€” the assistant answers instantly, and knows which page you're on * Click **"Talk to a Human"** at any point to bring the Lleverage team into the conversation * Use **"Report an issue"** next to the chat bubble to file a bug * If a request shows an error, use the "Report a bug" button on the error itself β€” it sends the technical details along automatically ### Best Practices #### For Efficient Task Completion * **Review Thoroughly**: Read all provided information before taking action * **Act Promptly**: Complete requests quickly to avoid workflow delays * **Provide Quality Input**: Ensure accuracy and completeness for input requests * **Verify Decisions**: Double-check approval choices before confirming #### For Effective Inbox Management * **Regular Monitoring**: Check your Request Inbox at consistent intervals * **Use Saved Views**: Save your common filter combinations and set your default landing view * **Keep It Tidy**: Archive requests that no longer need action * **Review Patterns**: Monitor completed requests to identify process improvements #### For Team Collaboration * **Reassign Rather Than Wait**: Hand requests over for holiday cover or workload balancing * **Use Notes and Mentions**: Keep the discussion on the record where everyone can see it * **Assign to Roles**: Role-based assignment spreads work across the team automatically * **Give Feedback**: Rate AI-generated content so builders can keep improving the workflow > πŸ’‘ **Workflow Success**: The Request Inbox is essential for maintaining smooth human-in-the-loop workflows. Regular monitoring and prompt action ensure your automated processes run efficiently while preserving necessary human oversight. ### Troubleshooting **Common Issues and Solutions** **Not receiving request notifications** * Check your notification settings in your user profile * Verify you're assigned to the correct role or user group * Confirm your organisation permissions **Requests not appearing in inbox** * Check the "Hide Completed" and "Hide Responded" filters β€” they're on by default * Check if you're viewing the correct organisation/project * Remember that non-Builders only see requests assigned to them **Cannot complete a request** * You can only submit requests you're assigned to β€” others open read-only * Check if the request has already been completed or superseded by someone else * Verify all required fields are filled correctly --- # 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://docs.lleverage.ai/platform/request-inbox.md?ask=&goal= ``` `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.