Check App Role
The Check App Role block evaluates whether the current user has been assigned a specific role within the app, then routes the workflow down one of two branches depending on the result.
Branch workflow based on user app role
The Check App Role block evaluates whether the current user has been assigned a specific role within the app, then routes the workflow down one of two branches depending on the result. It takes a role name as its primary input and compares it against the roles assigned to the current user. If the user holds that role, the workflow transitions to the configured "has role" path; if not, it follows the "no role" path instead.
The block outputs two values: a boolean field called hasRole indicating whether the user matched the specified role, and a userRoles array listing all roles currently assigned to that user. These outputs can be referenced downstream in the workflow for additional logic or display purposes.
This block fits into workflows where access control or personalization is needed — for example, showing different content to administrators versus standard users, or restricting certain workflow steps to users with a particular role. It is configured with optional step and workflow IDs for each branch, giving builders flexibility in how the two paths are structured.
What you can build
Real-world workflows powered by the Check App Role block.
Admin-Only Feature Access
Route users with an admin role to a management dashboard while redirecting standard users to a read-only view.
Tiered Content Delivery
Check whether a user holds a premium role before granting access to advanced content or features within the app.
Conditional Form Submission
Allow only users with an approver role to submit or finalize a form, sending others to a pending-review step.
Role-Based Onboarding Paths
Direct new users through different onboarding workflows depending on whether they have a manager or contributor role assigned.
Audit Log Visibility
Expose audit trail data only to users assigned an auditor role, keeping sensitive logs hidden from general users.
Support Escalation Routing
Automatically escalate a support ticket to a specialized workflow when the current user holds a senior-support role.
Ready to add Check App Role to your workflow?
Get Started FreeCommon questions about Check App Role
What parameters does the Check App Role block require?
The block requires a roleName string specifying which role to check against. Optionally, you can configure hasRoleStepId or hasRoleWorkflowId to define where the workflow goes when the user has the role, and noRoleStepId or noRoleWorkflowId for when they do not.
What does the block return as output?
The block outputs two fields: hasRole, a boolean that is true if the current user holds the specified role, and userRoles, an array of strings listing all roles assigned to that user.
What happens if no 'no role' path is configured?
If the user does not have the specified role and no noRoleStepId or noRoleWorkflowId is configured, the block will error rather than silently continuing.
Where are role names defined?
Role names are defined by the app creator through the app roles system. The roleName field in the block must match a role name as configured in that system.
What kinds of workflows commonly use this block?
This block is commonly used in workflows that require access control, content gating, or personalized routing — such as separating admin and standard user experiences, restricting form submissions to specific roles, or branching onboarding flows based on a user's assigned role.
Related capabilities
[YouTube] Search Trends
Retrieve trending videos on YouTube by category and region.
[Facebook] Scrape Posts for Page
Get all the posts for a Facebook page
Run Packaged Workflow
Run a packaged workflow ("custom block")
Run Connector from MindStudio Connector Registry (MSCR)
Run a raw API connector to a third-party service
Track Website Changes
Detect changes to a website
Add Check App Role to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.