Firestore Document Reads and Writes

Firebase Admin gives server side access to Firestore collections, letting a process read and write documents directly rather than through client app rules. A Beam agent starts a document update when an approved event happens elsewhere, such as an order status change, reads the matching Firestore document by its ID, and writes the new field values under the account's approved data rule. The agent notifies the owning system once the write completes. Documents that fail a write due to a permissions conflict, or updates that touch fields outside the agreed scope, get routed to a human before anything is retried.

User Account Management via Auth

Firebase Admin can look up, create, disable, or reset a user account in Firebase Authentication without the user needing to be signed in. A Beam agent acts on an approved request, such as a password reset ticket, reads the user's account by email or ID, and applies the approved change through the Admin API. The agent then notifies the requester once the action completes. Account deletions, role or permission changes, and any request that doesn't match an existing verified user get routed to a human before Firebase Admin makes the change.

Cloud Messaging Notifications

Firebase Admin can dispatch push notifications through Cloud Messaging to a specific device, user segment, or topic. A Beam agent fires off a notification when an approved condition is met in a connected system, such as a status change a customer is waiting on, reads the target device token or topic from the account record, and dispatches the message under the approved messaging template. The agent records the dispatch result against the source record. Notifications aimed at a broad audience, or any message wording outside the approved templates, get routed to a human to approve first.