Impact GateReference
Configure your workspace
Control default-branch synchronization, PR comments, and retained analysis history.
On this page
Save workspace preferences#
Open Settings
Go to Settings and confirm the intended workspace in the navigation.
Adjust Workspace preferences
An owner or admin with a verified email can change the editable preferences.
Choose Save preferences
Changes take effect after the server confirms the save. If someone changed the settings while you were editing, refresh and reapply your intended changes.
Available settings#
| Setting | Default / range | Effect |
|---|---|---|
| Analysis mode | Deterministic static analysis | The mode used by this deployment; the selector is read-only. |
| Sync default branch when code changes | Enabled | Default-branch pushes queue repository index refreshes. |
| Publish findings as pull request comments | Enabled | The App publishes and updates report comments. Disabling it does not disable analysis or checks. |
| Allow external model analysis | Unavailable | External model processing cannot be enabled on this deployment. |
| Add optional model summary to PR comments | Unavailable | When enabled on a capable deployment, model prose explains the deterministic report only; it cannot change the tier, findings, or evidence. |
| History retention in days | 90 by default; 7–365 days | Controls retained job and PR analysis history and evidence review records. |
Retention cleanup runs periodically. Current repository snapshots remain while their repositories are selected. GitHub comments are hosted in GitHub and are not removed by workspace history cleanup. Encrypted backups have a separate retention schedule.
Service names and criticality#
Service names are discovered from repository and manifest information, such as package.json or spring.application.name. You can set a discovered service's default criticality in a committed impact-gate.yaml file at its service root, then re-index the repository.
# Example: place this at the service root.
criticality: high
spec:
path: openapi.yamlSupported criticality values are high, medium, and low. The default is medium; configured workspace criticality rules can take precedence. The current Settings screen does not provide a criticality rule editor. The spec.path entry helps identify a missing or invalid configured document; the file must still satisfy supported contract requirements.
Connections and capabilities#
Sign-in methods shows your account's enabled provider connections. GitHub App shows the connected organization and installation state; choose Manage connection to reconnect authorization. Repository access is controlled by the App installation in GitHub.
Runtime observability connections lets owners and admins enter source access, discover service names, review suggested repository matches, and connect existing Prometheus and Datadog sources. Clear matches are preselected, exceptions use dropdowns, and Use all suggested matches applies proposed matches together. Query settings and manual aliases are optional advanced controls. Saved connections support edit, sync, and disconnect. Follow the connection guide for credentials, instrumentation, and coverage limits.