# Configuring SecOps

Settings controls the data and rules behind the screens. Environment owners and admins can edit a settings draft, review the changes and apply them together. Unsaved edits stay in that editor; applied settings are shared.

## What each setting changes

| Setting | Purpose | Guide |
| --- | --- | --- |
| Time to fix, by severity | Remediation allowances for Critical, High, Medium and Low | [Deadlines](/docs/secops/deadlines) |
| Owner rules | Exact repository or target-to-team mappings | [Ownership](/docs/secops/ownership) |
| Jira tickets | Read/send connections and project routing | [Tickets](/docs/secops/tickets) |
| Access log sources | Which provider accounts and events are read | [Setup](/docs/secops/setup#add-access-sources) |
| Access rule windows | Inactivity, credential use and key-lifetime limits | [Access](/docs/secops/access#inactivity-and-credential-windows) |
| Expected activity | Actor and action rules that suppress event-based attention | [Expected activity](/docs/secops/access#expected-activity) |
| People | Link GitHub and Workspace accounts and select a person's team | [Identity matching](/docs/secops/ownership#match-provider-accounts-to-people) |

## Review and apply a draft

While your draft differs from what is in force, a bar counts the changes. **Discard** removes the draft. **Review and apply** lists the differences; **Apply** saves them.

Read the effect, not only the new value. Changing a deadline can alter the overdue count without fixing a finding. A broad expected-activity rule can hide unrelated events from attention. Removing a source changes coverage rather than establishing that its accounts or findings disappeared.

Derived findings take the settings on the next model run. New source connections also need their pulls to complete. Settings that affect access reads can change what you see before a new provider state arrives, so check freshness and coverage after applying.

## App updates

When an app update needs an admin's attention, Settings shows the update and its outcome. Apply the offered update and check its reported result rather than assuming a newer set of tables was built because the screen reloaded.

## Check a change

After applying, inspect a representative finding or account affected by the rule and compare it with the source. Check unowned and shared fixes after changing ownership, and inspect expected events after editing suppression rules.

The app is currently for environment owners and admins. Configuring a source or a team is not a grant of member access.

## Uninstalling

**Danger zone → Uninstall app** previews what SecOps owns and will remove. App-created sources are removed only if you choose that option; your own sources remain. See [the overview](/docs/secops/overview#uninstalling).