# `AshScim.Test.PolicyExample.User`
[🔗](https://github.com/ash-project/ash_scim/blob/main/test/support/policy_example/user.ex#L5)

Fixture for verifying that `AshScim.Checks.AshScimInteraction` bypasses
policies that would otherwise forbid every action.

Without the bypass, every policy below would reject the router's reads,
creates, updates, and destroys outright.

# `t`

```elixir
@type t() :: %AshScim.Test.PolicyExample.User{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  aggregates: term(),
  calculations: term(),
  email: term(),
  id: term(),
  scim_external_id: term()
}
```

# `default_short_name`

# `input`

```elixir
@spec input(values :: map() | Keyword.t()) :: map() | no_return()
```

Validates that the keys in the provided input are valid for at least one action on the resource.

Raises a KeyError error at compile time if not. This exists because generally a struct should only ever
be created by Ash as a result of a successful action. You should not be creating records manually in code,
e.g `%MyResource{value: 1, value: 2}`. Generally that is fine, but often with embedded resources it is nice
to be able to validate the keys that are being provided, e.g

```elixir
Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()
```

# `input`

```elixir
@spec input(values :: map() | Keyword.t(), action :: atom()) :: map() | no_return()
```

Same as `input/1`, except restricts the keys to values accepted by the action provided.

# `primary_key_matches?`

---

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