# `AshScim.Checks.AshScimInteraction`
[🔗](https://github.com/ash-project/ash_scim/blob/main/lib/ash_scim/checks/ash_scim_interaction.ex#L5)

Returns `true` when the changeset/query has `context.private.ash_scim?`
set, which `AshScim.Router` does for every internal Ash call.

Add a bypass for this check on any resource exposed via SCIM so the
router's internal queries (read, get, create, update, destroy, load,
bulk_destroy) aren't blocked by your application's user-facing policies:

    policies do
      bypass AshScim.Checks.AshScimInteraction do
        authorize_if always()
      end

      # ...your normal policies...
    end

This mirrors the
`AshAuthentication.Checks.AshAuthenticationInteraction` pattern and serves
the same purpose: keep user-facing policies in charge of user-facing
actions, while letting the extension's plumbing run unimpeded.

# `eager_evaluate?`

# `init`

# `prefer_expanded_description?`

# `requires_original_data?`

# `strict_check`

# `type`

---

*Consult [api-reference.md](api-reference.md) for complete listing*