# `MishkaCmsCore.Accounts.UserIdentity`
[🔗](https://github.com/mishka-group/mishka_cms_core/blob/v0.0.1/lib/mishka_cms_core/accounts/user_identity.ex#L5)

One sign-in provider an account has used: AshAuthentication's user identity, a row per provider
per account, keyed on the provider's stable user id (`uid`, its `sub`) — never the email. Google,
GitHub and Slack can all sit on one account. See `MishkaCmsCore.Accounts.SignInProvider`.

Kept per site, as accounts are: the same Google account signs in to each site as that site's own
account. A master's identities have no site. Unique on the provider and its user id within a site,
and among masters (`nils_distinct? false`), so a sign-in updates the row it made before.

# `t`

```elixir
@type t() :: %MishkaCmsCore.Accounts.UserIdentity{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  access_token: term(),
  access_token_expires_at: term(),
  aggregates: term(),
  calculations: term(),
  id: term(),
  refresh_token: term(),
  site: term(),
  site_id: term(),
  strategy: term(),
  uid: term(),
  user: term(),
  user_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*