Administration Settings
How the in-app Settings screen is organized: main tabs and sections map to System Administration documentation so you can jump to the right guide.
Help Center
Browse articles in this category, or use search to jump to a specific task.
20 articles.
Settings > Configuration > Server Connection: point Studio at the Shift-Left Engine URL, view status, and reconfigure when you change environments.
Settings > Configuration > Proxy Settings: enable proxies separately for Shift-Left Engine and Shift-Left Agent based on execution mode.
Read your licence state — Active, Trial, Grace Period, Expired, Revoked, Offline — update the licence key, and understand what each state means for your team.
Settings > Licensing & Users > User Management: search users, review limits, add users, and edit or delete accounts (role and status).
Settings > Licensing & Users > Role Permissions: pick a role, then allow or deny grouped capabilities; reset to default or save changes.
System-wide rules for who can sign up and how: public registration, admin approval, email verification, default role, user caps, and password requirements.
Connect your identity provider (Entra ID/Azure AD, Okta, Google Workspace, or any OIDC/SAML IdP) so users sign in with corporate credentials, with group-to-role mapping.
Create scoped, rotatable API keys for programmatic access to the platform, with a grace window on rotation and immediate revoke—an alternative to username/password login.
Settings > Integrations > AI Settings: enable the AI engine, choose from ~20 model providers (including self-hosted), manage API keys, and test the connection—system-wide.
Settings > Integrations > Public API: Swagger and base URL, enable API, rate limits, token expiry, and which roles may use the API for CI/CD.
Connect HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault so test credentials are resolved at runtime with a secretref:// reference instead of being stored in the app.
Register outbound webhooks that POST signed event notifications to external URLs—for example when a test run completes—with a signing secret, test/redeliver, and a delivery log.
A Model Context Protocol (MCP) server for plugging Shift-Left Studio into AI agents like Claude and Cursor is in development. Not shipped yet — see what you can do today via the Public API.
Create the mail profiles that let Shift-Left API send notifications: SMTP and IMAP hosts, ports, security, and credentials — with the usual provider gotchas.
Manage the templates behind notifications: summary, detailed, and custom; categories for reports, system alerts, and test notifications; search and edit.
Monitor user activity and system events: summary tiles, filters by action, entity, role and status, and per-change field-level before/after detail.
Configure log level, file output, rotation and retention, and the sensitive-field redaction list — plus why Debug level is a temporary tool, not a default.