Admin Console

The Primitive Admin Console is a web-based dashboard for managing your apps, users, and backend configuration. It's available at admin.primitiveapi.com.

What You Can Do

App Configuration

• View and update app settings (name, mode, allowed origins)
• Manage app secrets (values write-only — never displayed after saving) and non-secret config vars (values shown in plain text)
• Configure authentication providers (Google OAuth credentials, email sign-in, Passkeys) — the Google client secret is picked from the app's secrets: the setting stores a {{secrets.KEY}} reference, never the secret itself
• Manage email templates for authentication flows
• Set invite-only mode for controlled access
• Manage the per-app whitelist for +primitivetest test-user sign-ins (see Authentication)

Users & Groups

• View all users in your app
• Invite new users and manage pending invitations
• Enable member invitations and set quota limits
• View pending invitations and the email-based document shares or group adds attached to them
• Manage console admins (who can access the admin console) and admin invitations
• Manage waitlist (when in invite-only mode)

Sharing & Access

• Review and approve/deny pending document access requests
• Browse a user's owned and shared documents
• View audit trail of share, invitation, and access-request activity

Databases

• Browse databases and their types
• Grant group-based permissions on a database

Prompts

• View managed prompts and their configurations
• Preview rendered prompts with test inputs
• Run prompt test cases
• See each prompt's availability (active or inactive) and change it with Disable/Enable

Integrations

• Configure external API connections (base URL, allowed paths, headers)
• Reference credentials from App Secrets as {{secrets.KEY}} in defaultHeaders or staticQuery
• Test integrations with sample requests
• View recent call logs

Email Templates

• Manage the built-in email templates (the full type list is in Email Templates)
• Register custom email template types with arbitrary kebab-case names
• Preview rendered templates and send test emails

Blob Buckets

• Create and configure blob buckets (access policy, retention tier, access rules)
• Browse blobs and generate signed URLs for inspection
• Delete buckets and their contents

Analytics

• View usage metrics and event counts
• Monitor daily active users
• Track custom events
• See Analytics for the emit and query APIs that feed this view

Connections

• Look up the connections that are live right now for one document or user
• See what each connection is bound to — a document, a realtime channel, or a user's notification channel — plus when it connected and when it expires
• The same view from the terminal is primitive connections list (see Inspecting and Debugging)

When to Use the Console vs. the CLI

Both tools manage the same configuration. In practice, many developers use the console for exploring and testing, and the CLI (with primitive config) for managing configuration as code — see Console or Code? for the full breakdown.

Next Steps

• Primitive CLI — The command-line side of the same configuration
• Prompts — Author the prompts you'll preview and test in the console
• API Integrations — Configure the integrations you'll manage in the console
• Analytics — Emit and query the events that show up under Analytics