🎭Roles and navigation

Give different signed-in people different menus — without maintaining separate apps.

NotionApps does not ship a separate “multi-role navigation editor” with many named role trees. Audience menus are built from navigation visibility and Screen Visibility Logic on logged-in user fields (for example a Role property on the Users database).

When you need this

• Managers see Approvals; staff see Submit forms

• Clients see a portal subset; internals see Operator tools

• One app URL, multiple audiences

Typical setup

1. Add a property on the Users database that distinguishes audiences (commonly Role, Type, or Plan).

2. Ensure every App User has the correct value.

3. For each screen, configure visibility:

   • Guest vs signed-in navigation toggles

   • Screen Visibility Logic using logged-in user fields (example: Role is Manager)

4. Optionally organize desktop items with Navigation Groups and App Navigation.

5. Publish, then verify with View as any user and a real login for each audience.

Screen Navigation Visibility

Deep reference: Screen Navigation Visibility.

Automation “Role” fields

Approval / Messaging wizards may ask for a Role field on the Users sheet for routing audiences. That is an Automation configuration concern — related, but not the same control as app chrome visibility. See Automation and Configure app audience and notification prefs.

Related

• App Users

• Auth and access

• Per-screen public access