New here, or not sure what is left? The guided setup walks through everything, one step at a time, with the setting we recommend.
Start the guided setupThis is a snapshot of accounts, streams, and Network health. Check it when reviewing activity or investigating a service problem; larger counts mean more activity, while memory and uptime describe this server.
This describes the Network process running on this server. Check it when investigating downtime or high memory use; more memory means less room for other work.
These are Network accounts and the access each person has. Use search to find someone, then change access or help recover their account; role changes apply immediately and can be reversed by selecting the previous role.
These are streams currently live on OpenVibe.Live. Review them during moderation; ending a stream disconnects the broadcast, and the streamer must start again to resume.
These are channel or owner references Live could not match during the last 30 days. Check them when a linked channel is missing, then correct the reference in the service shown as the last caller.
Use a channel link or stable account ID when correcting a reference. A display name alone cannot identify the channel.
These people are currently banned on Live. Review the reason before restoring access; allowing access again removes the restriction, and a new ban can be applied from Users if needed.
Search stored chat messages to investigate a report. Enter message text or a person below, then review the results before taking action.
Enter a search query or user ID
These people can moderate across Live channels. Add a trusted person when more coverage is needed; Remove moderator access reverses the promotion.
These settings control Network and its connected Live service. Choose a section before editing, and keep previous values so you can restore them after saving.
These are the services that read text aloud. Check this panel when reviewing available voices or diagnosing speech playback.
Billing holds every creator's balance. Its staff console lists cashouts still in escrow, ready to pay, paid and denied. Approving one records the payout reference; denying one puts the amount back in the creator's balance. The money freeze is there too.
Sign in with your OpenVibe account. Billing lets in the admins listed in its BILLING_STAFF_SUBJECTS setting.
These settings control the payment choices and prices Live shows. Review them before offering paid features; Billing handles the payment itself and any refunds.
Every AI job the network does, one step at a time. Add a key, run a tiny real request, and the route is ready. Keys are sealed in OpenVibe.AI and never shown again.
These are the limits and maintenance tools for shared text and image pastes. Check limits when reviewing capacity, and delete copies only when you intend permanent removal.
This shows how much space recordings and other files use. Review it when storage runs low; deleting recordings is permanent and requires a separate backup to recover.
Broadcasts send a notification to every user. Use them for network-wide announcements; sending cannot be recalled here, so send a correction if needed.
This sends the title and message to every user across OpenVibe. Review the wording and destination before sending; there is no recall control here.
This delivers the notification to all users. It cannot be recalled here; send a correction if needed.
Admins can send one global notification every 6 hours. Owners are exempt.
Network sends recovery and notification emails through Resend. Change the sender or delivery switch when configuring email, then send a test to check it.
This is the history of administrative changes. Review it after an unexpected change, then use the relevant settings page to correct it.
This records staff moderation actions across services. Filter it when investigating who acted and why; viewing or exporting the log changes no account permissions.
Staff actions reported by Chat, Live, Community, Tips, Billing and the other services (Tools, Games, Wiki, Blog, News, Reviews, Deals, Coupons, Trade, Codes). Each service enforces its own moderation; this is the record.
This checklist shows whether key operational areas are ready. Open the linked page when an item needs attention; a missing console means the listed command or API is the available route.
Every operator job the old admin did, and where it is done now: a tab here, another service's console, the host CLI, or an API that has no console yet (shown, not hidden). The dot is that service's readiness as the status page last saw it.
These themes are waiting for staff review. Approve a suitable theme to publish it, or reject it with a reason so its author can fix and resubmit it.
Community themes waiting for review. Approving one puts it in the public catalog; rejecting needs a reason, which the author sees. Values are already limited to the shared colour tokens.
These permissions let one OpenVibe service call another. Add one only for a required integration; revoke it to stop that access, or grant it again to restore access.
What each service may ask other services for. Tokens carry a change within 5 minutes. Every change needs a reason, is audited below and is announced as network.principal_grant.changed. Defaults come from the code.
These are event messages that have not reached a subscribed service. Fix the delivery problem before retrying; replay sends another delivery and cannot be recalled once sent.
Deliveries OpenVibe.Events could not make. A dead delivery stopped retrying; replay it once its consumer is fixed. Replays are audited.
These charts count visits, requests, errors, and response times. Choose a time range or service when investigating a trend; a longer range shows more history and a shorter range highlights recent changes.
This plots requests over the selected time range. Use a shorter range to inspect a spike or a longer range to compare activity across days.
This compares traffic across services. Review it when deciding which service needs more capacity or investigation.
This plots estimated distinct visitors over time. Compare periods to see audience changes; larger counts mean more visitors, not necessarily more registered accounts.
This compares visits with and without a signed-in account. Review it when checking how much activity comes from members versus visitors.
This compares each service’s portion of recorded traffic. Use it to identify where most requests go before changing capacity.
This compares estimated distinct visitors by service. Review it when checking audience size; a person visiting multiple services may be counted in each.
This plots each service’s traffic across the selected range. Review it when a network-wide spike needs tracing to one service.
This separates requests classified as automated from those classified as human. Check it when traffic rises unexpectedly; the classification is an estimate.
This estimates data transferred and request volume. Check it when planning capacity; more bytes mean more network use, not a confirmed bill.
This lists request totals and errors for each service. Review services with more errors before changing their configuration.
These addresses route people to tools across OpenVibe. Add or change an address when introducing a domain; remove the saved override to return to the built-in routing.