Repair live watchlist frontdoor routing
This commit is contained in:
@@ -52,10 +52,12 @@ A watchlist entry defines an identity pattern to monitor and alert configuration
|
||||
|
||||
| Scope | Description | Who Can Create |
|
||||
|-------|-------------|----------------|
|
||||
| `tenant` | Visible only to owning tenant | Any user with `watchlist:write` |
|
||||
| `global` | Shared across all tenants | Administrators only |
|
||||
| `tenant` | Visible only to owning tenant | Any user with `trust:write` |
|
||||
| `global` | Shared across all tenants | Administrators with `trust:admin` |
|
||||
| `system` | System-managed entries | System only |
|
||||
|
||||
Console and frontdoor watchlist flows use the canonical trust scope family: `trust:read`, `trust:write`, and `trust:admin`. Legacy `watchlist:*` aliases remain accepted for older clients, but new integrations should use the trust scopes.
|
||||
|
||||
## CLI Usage
|
||||
|
||||
### Adding a Watchlist Entry
|
||||
|
||||
Reference in New Issue
Block a user