Skip to main content

Admin Panel Roles and Permissions

Role-based access keeps daily operations separate from production configuration. Use one named account per person and assign the smallest role that allows the work they need to do.

Role Summary​

RoleBest forTypical access
ownerProduct owners, technical leads, and trusted administratorsFull setup, team access, settings, operations, support, moderation, campaigns, imports, exports, and audit review.
operatorOperations staffBusiness workflows such as orders, bookings, trips, listings, driver availability, provider readiness, imports, and exports.
supportCustomer supportUser lookup, account review, support actions, user timeline context, and read-only operational context.
moderatorTrust and safety teamsReports, user-generated content review, dating safety, social moderation, hide/show actions, and escalation handling.
content_managerContent, catalog, and marketing teamsProducts, listings, media, templates, campaigns, featured content, categories, and safe content updates.

First Owner Setup​

The first owner is created before the Admin Roles page can be used.

Recommended flow:

  1. Create the user in Firebase Authentication.
  2. Assign role: "owner" with Firebase Auth custom claims or a Firestore users/{uid} document.
  3. Sign in to the admin panel.
  4. Open Admin Roles.
  5. Add the rest of the team from the dashboard.

After the first owner exists, avoid changing roles directly in Firebase Console unless you are recovering access.

Permission Boundaries​

Use these boundaries when assigning roles:

AreaRecommended roles
App Settings and launch configurationowner
Admin Rolesowner
Audit Log reviewowner, operator when operational review is needed
Support Cockpitowner, support, operator
Campaignsowner, content_manager, operator
Media Libraryowner, content_manager, operator
Commerce, appointments, taxi, listings workflowsowner, operator
Social moderation, reports, dating safetyowner, moderator
Catalog, listings, templates, contentowner, content_manager, operator

Solo Operator​

  • one owner account for setup;
  • one separate operator or support account for day-to-day testing.

Do not use the owner account for every routine action. Keeping daily work in a separate role makes Audit Log easier to understand.

Small Operations Team​

  • founder or technical lead: owner;
  • operations lead: operator;
  • support agent: support;
  • content or catalog manager: content_manager;
  • trust and safety reviewer: moderator.

Agency Or Implementation Partner​

  • product owner: owner;
  • implementation partner: temporary owner;
  • operations lead: operator;
  • support team: support;
  • content team: content_manager.

Remove temporary owner access after setup is complete.

Production Access Rules​

Before production:

  • use named accounts, not shared logins;
  • keep at least two owner accounts for recovery;
  • remove inactive admins;
  • remove implementation-only access after setup;
  • use the smallest practical role for every person;
  • review Audit Log during the first production week;
  • rotate temporary credentials used during setup.

Recovery​

If all owner accounts are locked out:

  1. open Firebase Console;
  2. find the intended owner in Authentication;
  3. restore role: "owner" using custom claims or users/{uid};
  4. sign in to the admin panel;
  5. review Admin Roles and Audit Log.

Next Steps​