Open Project Settings → Auth to configure Authentication. Everything on this page is optional — Authentication works with Firebase Auth fields alone if you skip it.
Linking a Profile Collection
Most apps store additional user data (name, avatar, preferences, plan, etc.) in a Firestore collection alongside Firebase Auth. Linking that collection lets Firepanel show and edit it right on the user's detail page.
Pick a collection
Choose the Firestore collection that holds your own user data.
Choose how it's matched to a user
- Document id is the uid — the collection is keyed directly by uid (e.g.
profiles/{uid}). Fastest option, no extra field needed. - Match by field — pick a field on the documents that holds the uid; Firepanel queries for it instead.
Save
Click Link a collection (or Save if editing).
Click Re-check at any time to scan your Firebase Auth users and see how many currently match a profile document.
Note:
Unlinking a profile collection also clears any configured related collections and profile columns, since they depend on the link.
Users List Columns
Once a profile is linked, a Users List section lets you pick up to 4 profile fields to show as extra columns on the users list.
Related Collections
A related collection is any Firestore collection that stores the user's uid on each document (for example, an orders collection with a userId field). Once configured, matching records for a user appear on their detail page.
Add a collection
In the Related Collections section, click Add collection.
Configure the match and display
- Pick the collection and the field holding the uid
- Choose to display matches as a Table or as Cards (Media & title, or Label & value rows)
- Pick which fields to show, and a media field for card layouts
- Set how many rows to show per page (5/10/25)
Save
Click Save. Repeat for as many related collections as you need.
Indexing
Firebase Auth has no built-in search, filtering, or server-side sorting, and no way for Firepanel to be notified when users change. To support search and filtering on the users list, Firepanel can maintain its own index of your Auth users — but only if your project has Algolia or Elasticsearch configured under Full-Text Search; Firestore-native search can't cover Auth users since they aren't a Firestore collection.
Note:
Changes made directly in the Firebase console aren't reflected until the next sync — Firebase Auth doesn't notify Firepanel of changes made outside it.