How do I set up user roles and permissions in my app?

Fuzen apps use role-based access control (RBAC) so you can decide exactly what each user can see and do. Roles are managed from the Manage App Settings page.

Default roles

Every Fuzen app comes with default roles. For example, a typical app includes:

• App Editor — Can edit the app structure and content
• Admin — Full access to all data and settings
• Employee / Viewer — Limited access based on role configuration

The exact default roles may vary depending on the template or how the app was built.

The Roles tab in Manage App Settings. Existing roles are on the left; create new ones using the Add New Role form on the right.

Creating new roles

1. Click the widget (blue pencil icon at the bottom-left corner)
2. Select Manage App Settings
3. Go to the Roles tab
4. In the "Add New Role" section, type a label for the new role (e.g. "Teacher", "Sales Rep", "Customer")
5. Click Add
6. The new role appears in the "Roles for this app" list below

Assigning roles to team members

After creating roles, assign them to users from the Team tab in Manage App Settings. When inviting a new user, select the appropriate role(s). For existing users, click the edit icon next to their name to change roles.

The AI Chat Canvas. Describe your access rules in plain language and the AI applies page-level, record-level, and action-level permissions.

Configuring what each role can access

To control which pages, data, and actions each role has access to, use the chat canvas (AI editor). Open it by clicking the widget → Edit With AI, or by clicking the Magic Wand icon on the right side of the screen. Then describe your access rules in plain language:

• "The Billing page should only be visible to Admins. Hide it from Employees."
• "Sales Reps should only see leads assigned to them, not all leads."
• "Add a Teacher role that can see only their assigned class's students."
• "Only Admins can delete records. Editors can create and edit but not delete."

The AI will apply page-level visibility, record-level filtering, and action-level restrictions based on your description.

Best practices

• Default to least access — Start with minimal permissions and add more only when needed
• Test every role — Create a test user for each role and verify they only see what they should
• Use role-based filtering for sensitive data — "Show only records where assigned_to equals the logged-in user"