Operations
Settings & Admin
Workspace config, Bison tokens, user management
What This Does
Settings manages workspace configuration, external service credentials, and user access. Each workspace has its own Bison token, filter rules, and contact targets.
Workspace Configuration
Bison Tokens
Each workspace needs an active Bison API token to sync campaigns and upload leads.
- Go to Settings → Bison Tokens
- Each workspace shows its token status (
active/expired) - To refresh: click the workspace, enter new token from Bison dashboard
- Tokens are stored in the
bison_tokenstable withis_active=True
Client Registry
The client_registry table maps workspace names to display names and configuration:
workspace_name: Internal snake_case name (e.g.,gregg_blanchard)display_name: Human-readable name (e.g., "Gregg Blanchard")bison_workspace_id: Links to Bison workspace (IDs 14 and 15 are anomalous — reassigned to different clients)monthly_contact_target: How many contacts to upload per month
Monthly Targets
The monthly target counts contacts uploaded to Bison, not raw scraped. Pipeline progress is tracked via pipeline_stats_cache.uploaded.
User Management
Users are managed via Supabase Auth:
auth.usersmust exist before creatinguser_profilesoruser_workspace_access- Workspace access is granted per-user in
user_workspace_accesstable - Users can have access to multiple workspaces
Common Issues
| Symptom | Cause | Fix |
|---|---|---|
| Token expired on campaign sync | Bison token needs refresh | Get new token from Bison dashboard, update in Settings |
| New user can't see any data | Missing workspace access | Add entry to user_workspace_access for the user + workspace |
| Workspace not appearing in dropdown | Not in client_registry | Add workspace to client_registry table |
Related Alerts
- BisonAPIHighErrorRate: May indicate token issues across workspaces