Organization Settings
Configure organization-level settings, manage team members, and control access.
Overview
Organization settings allow admins to:
- Manage team members and roles
- Configure API keys for LLM providers
- Set budgets and spending limits
- Customize organization preferences
- View audit logs for compliance
Accessing Settings
Navigate to Settings:
- Click your profile icon (top right)
- Select Settings from dropdown
- Choose Organization tab
Organization Profile
Basic Information
Organization Name
- Display name shown throughout the app
- Editable by admins only
- Used in reports and exports
Organization ID
- Unique identifier (auto-generated)
- Used for API integrations
- Cannot be changed
Created Date
- When organization was created
- Read-only
Plan Type
- Current subscription plan
- Free tier includes all features
- Usage limits may apply
API Key Management
Configure LLM provider API keys for your organization.
Adding API Keys
- Go to Settings → API Keys
- Click Add API Key
- Select provider:
- Anthropic (Claude)
- OpenAI (GPT-4)
- Google (Gemini)
- Perplexity
- Paste API key
- Click Save
Security: Keys are encrypted (AES-256-GCM) and never exposed in UI or client code.
Managing Keys
View Status
- ✅ Active - Key is configured and working
- ⚠️ Inactive - Key disabled or invalid
- 🔄 Testing - Key validation in progress
Edit Keys
- Click Edit to update an existing key
- Original key is never shown (security)
- Enter new key to replace
Delete Keys
- Click Delete to remove key
- Requires confirmation
- All team members lose access to that provider
Test Keys
- Click Test to verify key works
- Executes a simple query
- Shows result (success or error)
Key Scope
API keys are scoped per organization:
- All team members use org keys
- Individual API keys not supported (current version)
- Costs attributed to organization, not individuals
Budget Management
Set spending limits to control LLM API costs.
Monthly Budget
- Go to Settings → Budget
- Enter monthly limit (USD)
- Click Save
When budget is exceeded:
- Warning shown to all users
- Email alert sent to admins
- Queries can still execute (soft limit)
Budget Alerts
Configure alert thresholds:
- 50% - Warning notification
- 80% - Critical notification
- 100% - Budget exceeded notification
Alerts sent via:
- In-app notification
- Email (if configured)
Cost Tracking
View current spending:
- This month: Current month-to-date
- Last month: Previous month total
- All time: Lifetime organization costs
Breakdown by:
- Provider (Claude, GPT-4, etc.)
- Team member (who executed)
- Time period (daily, weekly, monthly)
Organization Preferences
Customize organization-wide settings.
Default Provider
Set default LLM provider for new queries:
- Applies to all team members
- Can be overridden per-query
- Helps standardize testing
Model Configuration
Choose specific models per feature:
- Query Generation: Model for generating queries from URLs
- Citation Analysis: Model for analyzing citations
- Default Model: Fallback for all features
See Model Configuration Guide for model details.
Data Retention
Configure how long data is kept:
- Query History: 30, 60, 90 days, or forever
- Responses: Same as query history
- Analytics: Aggregated (never deleted)
Feature Status
🚧 Partial Implementation
Current version includes:
- ✅ API key management
- ✅ Basic org info
- 🚧 Team management (placeholder)
- 🚧 Role-based access (planned)
- 🚧 Budget alerts (planned)
- 🚧 Audit logs (planned)
Planned Features
Team Management
Full team collaboration features:
Member Management
- Invite team members by email
- Assign roles (Admin, Member, Viewer)
- Remove members
- View member activity
Role-Based Access
- Admin: Full control (settings, billing, members)
- Member: Execute queries, view analytics
- Viewer: Read-only access to reports
Advanced Budgets
Enhanced budget controls:
- Per-provider budgets
- Per-member budgets
- Hard limits (stop queries when exceeded)
- Budget forecasting
- Cost allocation by project/tag
Audit Logs
Complete audit trail:
- Query executions
- Settings changes
- Member invites/removals
- API key modifications
- Export audit logs for compliance
Workarounds (Current Version)
Team Collaboration
Share access manually:
- Share Supabase credentials securely
- All users use same API keys
- Track costs manually in spreadsheet
Role Management
Implement manually:
- Use different Supabase projects for different teams
- Share API keys only with trusted team members
- Monitor usage through provider dashboards
Security Best Practices
API Key Security
✅ Do:
- Rotate keys periodically (every 90 days)
- Use separate keys for dev/staging/prod
- Monitor key usage in provider dashboards
- Delete keys when team members leave
❌ Don't:
- Share keys outside your organization
- Use production keys for development
- Commit keys to version control
- Share keys via email/Slack
Access Control
- Limit admin access to trusted members
- Review member list periodically
- Remove inactive members promptly
- Enable MFA on Supabase (when available)
Troubleshooting
Can't Save API Key
Symptom: "Failed to save API key" error
Solutions:
- Verify you're an org admin
- Check key format matches provider requirements
- Test key in provider dashboard first
- Check browser console for errors
Budget Not Updating
Symptom: Budget shows outdated numbers
Solutions:
- Refresh page (Cmd/Ctrl + Shift + R)
- Check Supabase for actual query data
- Verify cost calculation in Analytics
Settings Not Saving
Symptom: Changes don't persist after reload
Solutions:
- Check browser console for errors
- Verify RLS policies allow updates
- Try different browser
- Check Supabase status
Related Documentation
- Team Management - Collaborate with team
- Audit Logs - Track changes and activity
- API Keys Setup - Detailed key configuration
Next Steps
After configuring organization settings:
- Add team members (when available)
- Set up API keys
- Configure budgets
- Execute queries from the dashboard