CiteFoundry Docs
Open dashboard

Platform admin

For CiteFoundry staff and Business-tier owners — tenant management, processor caps, signal-source caps, scrape jobs.

The Admin section is for CiteFoundry platform operators and a small set of Business-tier customers with self-service tenant management. If you don’t see it in your dashboard, you don’t have access — that’s by design.

What’s in admin

  • Tenants — every organization on the platform. Inspect plans, member counts, run volumes, and suspension state. From here you can suspend, reinstate, or hard-delete a tenant.
  • Users — global user table. Resend invitations, check session state, force-revoke sessions.
  • Processors — the LLM provider integrations (OpenAI, Anthropic, Google). Per-processor health, per-tenant rate caps, the model catalog wired into the dashboard.
  • System prompts — the platform-level system prompts used during ingestion and analysis. Versioned; changes roll out at the next run.
  • Signal sources — caps on upstream-pull volume per integration (Google Search Console, Google Ads). Useful when a customer’s API quota is in trouble.
  • Scrape jobs — brand-page scraping queue with status, retries, and manual override.
  • Costs — cost-per-run analysis by provider, surface, and tenant.

Audit and safety

Every admin action is audit-logged with the actor, the target tenant or user, and a timestamp. The log is read-only and retained for the life of the organization.

Destructive actions (delete tenant, force-revoke session, drop scrape job) require a typed confirmation. There is no “undo” — there are exports if you need to preserve state before you act.

Access

Admin access is granted per-user by a Platform Owner. There’s no “give my whole team admin” toggle — the per-user grant is intentional.

API

Most admin endpoints sit under /v1/platform/... and require a token on a user with the platform_admin flag.

  • GET /v1/platform/tenants
  • GET /v1/platform/tenants/{tenantId}
  • POST /v1/platform/tenants/{tenantId}/suspend

The dashboard UI is the supported surface for most operations; the API is documented for completeness and for the few customers running custom admin tooling.