Settings
Workspaces, providers, and your local data.
Workspaces & white-label
Personal — Saiadmin
Client: Sai Prathyaksh KanagatRate: €60/hrLogo: — uses owl mark
Roles are advisory in v2.4: reviewer sees an approval prompt on the Pipeline instead of a Publish button, writer can't approve their own drafts, and admin can do everything. Multi-user enforcement lands when NextAuth is wired with a real DB.
Integrations
Checking integrations…
LLM provider
Configure your provider on the Guardrails page — your key is stored in browser session only and never sent to our servers.
Open provider settings →Account & token linking
Optional. NextAuth (Google) only activates when
AUTH_SECRET, AUTH_GOOGLE_ID, AUTH_GOOGLE_SECRET are set on Vercel. The sync-token model below still works without sign-in.Link platform connections to my account
Moves your cookie-sealed OAuth tokens (LinkedIn / X / Meta / GA4) into KV under your sync token. The Vercel cron uses these tokens to publish scheduled posts even when no browser is open.
Cross-device sync
Paste the same token on each device to sync your posts, leads, workspaces, and brand guide. No accounts. Tokens are opaque — keep yours secret.
Notifications (Slack / Discord / webhook)
Add a destination
Slack: create an Incoming Webhook in your workspace, paste the URL above. Discord: Server settings → Integrations → Webhooks. Generic: any HTTPS endpoint that accepts JSON POST.
No destinations yet. Add one above to start getting publish + watchlist + inbox pings.
Data
All posts, leads, and workspaces live in your browser (localStorage). Nothing is uploaded.
About
Content Vigilante is open source under MIT. GitHub →