AccessKit Pro is a centralized permissions and roles engine for Bubble apps. It helps you control which users can see pages, groups, buttons, tabs, popups, and workflows based on roles, permissions, scopes, overrides, expiration dates, and active status.
Use AccessKit Pro when your app has more than simple admin/customer access, such as managers, staff, vendors, drivers, accountants, store owners, clients, or team members with different access levels.

The plugin does not replace Bubble Privacy Rules. AccessKit Pro helps with UI visibility and workflow conditions. For real database security, always use Bubble Privacy Rules so unauthorized users cannot load private data from the database.

Main concepts:

Roles define what a type of user can usually do. Example roles: owner, admin, manager, staff, vendor, customer, driver, accountant.

Permissions define specific actions or areas of access. Example permissions: view_dashboard, manage_inventory, edit_booking, cancel_booking, refund_payment, view_reports, manage_staff, manage_settings, view_orders, approve_payouts.

User permission assignments connect a user to a role and optional scope. Example: Sarah is a manager for Store 123. Mike is staff for Store 456. Nina is accountant for all stores.

Scopes let you limit access to a specific store, company, vendor, team, location, project, or other record. Example: a manager can manage_inventory only for Store 123.

Permission overrides let you grant extra permissions to one user beyond their role.

Denied permissions let you block specific permissions for one user. Denied permissions always win over role permissions, overrides, and super admin access.

Expiration dates let you create temporary access. If the permission assignment has expired, access is denied.

Active status lets you turn a permission assignment on or off.

AccessKit Pro includes:

Access Guard: Checks one permission and publishes Allowed, Denied, Reason, Matched permission, Scope matched, and Expired states. Use Access Guard for one protected group, button, popup, page section, or workflow.

Access Map: Checks many permissions at once and publishes Allowed permissions, Denied permissions, Checked permissions, Allowed count, Denied count, and Summary. Use Access Map on dashboards, admin panels, portals, tab menus, URL-parameter menus, and pages with many protected sections.

Permission Debugger: Shows the input and result of a permission check for testing. Use it while building to understand why access was allowed or denied.

Check Permission action: Server-side action that checks one required permission and returns allowed or denied. Use it before important workflows, such as refunding a payment, editing a booking, inviting staff, or navigating to a protected page.

Check Multiple Permissions action: Server-side action that checks several permissions at once using all or any mode. Use it when a workflow should require multiple permissions or at least one permission from a group.

Format Access Log action: Server-side action that formats permission check results into clean log data. Use it with your own Bubble database workflow to create Access Log records.

Demo: https://addressflow-demo-page.bubbleapps.io/version-test/accesskit_pro?debug_mode=true

Editor: https://bubble.io/page?id=addressflow-demo-page&tab=Design&name=accesskit_pro&ai_generated=true&type=page&elements=bTHXl