Settings
Configure your Keva workspace, team, and AI behavior
The Settings page is your central hub for managing your Keva workspace. Review the Clerk roster, configure Keva roles and assignment behavior, and control AI behavior. Billing is not available in this release; no Settings > Billing section, card, or billing permission row is offered. Platform connections are managed on the top-level Integrations page.
Overview
Keva Settings is organized into logical sections:
- Team Management - View the Clerk roster and manage ticket assignment
- Roles & Permissions - Control who can do what
- API Keys - Manage programmatic access
- AI Configuration - Autonomy and trust controls
Accessing Settings
Navigate to Settings from the sidebar menu. Access requires the settings.view permission.
Settings Sections
Team
View Clerk members and manage ticket assignment
Roles
Configure roles and permissions
API Keys
Create and manage API keys
Permission Requirements
| Section | View Permission | Edit Permission |
|---|---|---|
| Team roster | team.view | Clerk membership lifecycle is external |
| Ticket assignment | team.view | settings.edit |
| Roles | team.view | team.edit_roles |
| API Keys | api_keys.view | api_keys.create, api_keys.delete |
| Connector access (RBAC) | connectors.view | connectors.create, connectors.edit |
| AI Settings | settings.view | settings.edit |
Quick Actions
Create an API Key
- Go to Settings > API Keys
- Click Create Key
- Enter a descriptive name
- Copy the key immediately (shown only once)
Connect WordPress
- Go to the top-level Integrations page.
- In the WordPress connection, enter your site URL and follow the guided setup.
- Return to the WordPress connection section to confirm the site is connected.
Best Practices
Role Assignment
- Start with the least privilege needed
- Use the Viewer role for stakeholders who only need read access
- Reserve Owner and Admin for trusted personnel
API Key Security
- Create separate keys for different integrations
- Rotate keys regularly
- Delete unused keys promptly
Audit Trail
Selected settings mutations have local audit custody. This is not proof that every settings change is logged or that SOC 2 readiness has been achieved. Review available events at Settings > Audit Log.