Lewati ke konten utama

Server Administration

Server administration features in ChurchApps are available only to users with the Server.Admin permission. These tools are used for platform operations, support, and troubleshooting across all churches in the system.

Access Restricted

The features described on this page require Server.Admin permission and are not available to regular church administrators. They are intended for platform operators and support staff only.

Accessing Server Admin​

Users with Server.Admin permission can access the server admin panel from B1 Admin:

  1. Log in to admin.b1.church
  2. Click the Admin tab in the main navigation
  3. The Server Admin panel includes tabs for managing churches, users, and system operations

User Impersonation​

The impersonation feature allows server admins to log in as another user for support and troubleshooting purposes. This is useful when investigating user-reported issues or helping churches configure their systems.

How to Impersonate a User​

  1. Navigate to the Impersonate tab in the Server Admin panel
  2. Enter the user's name or email address in the search field
  3. Click Search or press Enter
  4. From the search results, click on the user you want to impersonate
  5. Confirm the impersonation in the dialog that appears
  6. You will be logged in as that user and redirected to their account

Important Notes​

  • Impersonation creates a new session with the target user's permissions and church access
  • Your original admin session ends when you impersonate another user
  • All actions taken while impersonated are logged in the audit trail
  • To return to your admin account, log out and log back in with your credentials
  • Use impersonation only when necessary for support purposes and always inform users when accessing their accounts for support

API Endpoint​

The impersonation feature is backed by the /users/:userId/impersonate endpoint in the Membership API. See Membership Endpoints for technical details.

Security Considerations​

  • Impersonation requires Server.Admin permission - this permission should be granted sparingly and only to trusted platform operators
  • All impersonation events are logged with the admin user ID and target user ID
  • Churches are not notified when impersonation occurs, so establish clear policies for when and how this feature should be used
  • Consider documenting impersonation events in your support ticket system for accountability

Commons Moderation​

Commons is the shared moderation queue for user-submitted content across products — WorshipCommons songs, Lessons.church lessons, FreeShow templates, and B1 website builder templates all flow through the same queue instead of separate per-product review tools.

Accessing Commons​

  1. Navigate to the Commons tab in the Server Admin panel.
  2. You will see three sub-tabs: Queue, Reports, and Assets.

A limited music editor role can also see the Queue tab, but is blocked from approving submissions that change a song's rights or licensing.

Queue​

The Queue lists every pending submission across all products, filterable by product and asset type. Each row shows whether the submission is a new asset, an edit by its original author, or an edit by a third party, along with the submitter's approval track record and how long the submission has been waiting (flagged once it passes 72 hours).

Click Review to open a drawer with field-level diffs, file previews, and an embedded read-only preview of the item. Use the a/r keyboard shortcuts to approve or reject, and j/k to move to the next or previous submission without leaving the drawer. Rejecting requires selecting a reason (for example quality, duplicate, licensing, ccli, ai, or off-topic) and a note.

Reports​

The Reports tab handles copyright and policy/quality reports filed against already-published assets, split into separate Copyright and Policy & Other queues plus a Resolved history. Claim a report to start working it, then resolve it with a resolution (upheld, dismissed, or duplicate) and an action (none, unpublish, or remove).

Assets​

The Assets tab is a searchable browser of published content with actions to Feature an asset (highlights it on the product's home page), Unpublish/Republish it, or Remove it (with a copyright or policy reason).

For songs specifically, this is also where a song becomes Sunday-ready and eligible to appear in a church's B1 Admin song search: a reviewer opens the asset and marks each published key as Listened once they've listened through it and confirmed the score, chords, and slides are all present. A song only becomes Sunday-ready once every key is checked off.

info

Commons moderation is staff-only — individual churches never see this queue. The one place an individual church's B1 Admin touches Commons data is the "WorshipCommons — free" section of the song search, which only surfaces songs that have already been through this review process.

See the Content Commons architecture page for the underlying data model and submission lifecycle.