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

# Organization settings

> Set your organization's display name, logo, and sign-in branding in Iru Identity so your people recognize the tenant they're signing in to.

Your **organization** is your tenant, the isolated Iru environment that holds
your directory, applications, policies, and settings. Organization settings are
where you set the details that identify your organization and shape how Iru
looks to the users who use it. Find them under **Organization** in the
Iru dashboard.

<Note>
  These settings apply to your whole tenant. Changes are visible to everyone in
  your organization, including end users on the sign-in screen and their
  app dashboard.
</Note>

## What you can set

<CardGroup cols={2}>
  <Card title="Display name" icon="signature">
    The name that represents your organization in Iru and that your people see
    as the organization providing their apps.
  </Card>

  <Card title="Branding" icon="image">
    Your organization's logo, shown to end users on the sign-in screen and on
    their app dashboard so the experience looks like yours.
  </Card>
</CardGroup>

## Display name

Your organization's **display name** is the friendly name your people associate
with their access. On the app dashboard, Iru welcomes each user and notes
that their applications are provided by your organization, using this name.

<Tip>
  Use the name your people already recognize (the same name they would expect
  to see on an internal portal) so the connection to your organization is
  obvious at sign-in.
</Tip>

## Branding

Add your organization's **logo** so Iru reflects your brand rather than a
generic identity screen. Upload an image as your organization icon, and Iru
shows it in the places your people encounter Iru. You can replace the logo at
any time, or remove it to return to the default.

### Where your people see it

```mermaid theme={null}
flowchart LR
  brand["Organization logo + display name"]
  signin["Sign-in screen"]
  dash["App dashboard"]
  brand --> signin
  brand --> dash
```

* **Sign-in screen.** Your logo and name appear as users authenticate, so they
  can trust they are signing in to the right place. See
  [The sign-in experience](/en/identity/authentication/sign-in-experience).
* **App dashboard.** Your branding carries through to the app launcher
  where users open their assigned applications. See
  [End-user experience](/en/identity/administration/end-user-experience).

<Info>
  Branding is about recognition and trust. A familiar logo and name reassure
  your people that the sign-in screen is legitimate, which is a small but real
  defense against look-alike phishing pages.
</Info>

## Related

<CardGroup cols={2}>
  <Card title="The sign-in experience" icon="right-to-bracket" href="/en/identity/authentication/sign-in-experience">
    See how your branding appears as your users authenticate.
  </Card>

  <Card title="End-user experience" icon="grip" href="/en/identity/administration/end-user-experience">
    See the branded app dashboard where your people launch their apps.
  </Card>
</CardGroup>