> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usetero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enforcement

> Where and how Tero enforces policies

After you approve a policy, choose where Tero enforces it. Some options apply on the next sync or provider API update, while others hand the work to your engineers.

<CardGroup cols={2}>
  <Card title="Enforce at edge" icon="server" href="/policies/enforcement/edge">
    Execute policies before data leaves your network. Drop, sample, transform, or redact data.
  </Card>

  <Card title="Enforce in provider" icon="cloud" href="/policies/enforcement/provider">
    Configure exclusion filters and routing rules through the provider API.
  </Card>

  <Card title="Open PRs" icon="code-pull-request" href="/policies/enforcement/open-prs">
    Fix instrumentation at the source. Tero opens the PR, your team reviews.
  </Card>

  <Card title="Create tickets" icon="ticket" href="/policies/enforcement/create-tickets">
    Assign work to engineers in Linear or GitHub Issues.
  </Card>

  <Card title="Notify" icon="bell" href="/policies/enforcement/notify">
    Alert teams in Slack or email.
  </Card>

  <Card title="Set SLOs" icon="bullseye" href="/policies/enforcement/set-slos">
    Quality targets for teams to meet. Track progress over time.
  </Card>
</CardGroup>

## Choose an enforcement method

| Method                                                                        | Resolution                                            | Reversible                                                 | Best for               |
| ----------------------------------------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------- | ---------------------- |
| <Icon icon="server" /> [Enforce at edge](/policies/enforcement/edge)          | <Badge color="green" icon="bolt">Next sync</Badge>    | <Badge color="green" icon="rotate-left">Reversible</Badge> | Most policy categories |
| <Icon icon="cloud" /> [Enforce in provider](/policies/enforcement/provider)   | <Badge color="green" icon="bolt">Provider API</Badge> | <Badge color="green" icon="rotate-left">Reversible</Badge> | No Edge deployed       |
| <Icon icon="code-pull-request" /> [Open PRs](/policies/enforcement/open-prs)  | <Badge color="orange" icon="clock">Variable</Badge>   | <Badge color="green" icon="rotate-left">Reversible</Badge> | Code-level fixes       |
| <Icon icon="ticket" /> [Create tickets](/policies/enforcement/create-tickets) | <Badge color="orange" icon="clock">Variable</Badge>   | N/A                                                        | Human decisions needed |
| <Icon icon="bell" /> [Notify](/policies/enforcement/notify)                   | <Badge color="orange" icon="clock">Variable</Badge>   | N/A                                                        | Awareness              |
| <Icon icon="bullseye" /> [Set SLOs](/policies/enforcement/set-slos)           | <Badge color="gray" icon="chart-line">Ongoing</Badge> | <Badge color="green" icon="rotate-left">Reversible</Badge> | Long-term tracking     |

Tero recommends an enforcement method for each policy category. You can override, combine, or change later.