> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/customize-app/types-of-screens/everyday-chrome-screens/profile.md).

# 👤 Profile

The **Profile** screen is the Everyday chrome preferences surface. End users choose their **default landing screen**, toggle notification preferences, save those prefs, and log out.

{% hint style="info" %}
**Who this guide is for**\
Makers who need a built-in settings page instead of a custom Profile form on a Notion users database.
{% endhint %}

### What the screen is for

Use Profile when users need to:

* Choose which primary screen opens after login
* Turn in-app / email notifications on or off
* Log out of a private app

**Good examples**

* Private field app: techs land on My Queue; supervisors land on Activity
* Portal users disable email notifications but keep in-app alerts
* Shared devices: clear logout from Profile

**Bad examples**

* Editing Notion user record fields (role, team, phone) → use an **Update Form** on the users database
* App-wide theme / density → use builder **Settings** (makers), not Profile
* Password reset / SSO admin → outside Everyday chrome

### Add Profile in the builder

1. Open **Screens → + New Screen**.
2. Choose a Notion database as the context anchor (often your Users database).
3. Under **Everyday chrome**, select **Profile**.
4. Click **Done**.
5. Place Profile last in navigation (side nav footer or More menu).

![Profile selected in the Everyday chrome picker](https://iili.io/CwBolhQ.png)

### What users see in the live app

Profile shows:

* **Default landing screen** list (primary screens in the app)
* **Notifications** toggles for in-app and email
* **Save preferences**
* **Log out**

![Profile — default landing screen picker](https://iili.io/CwBoXYg.png)

![Profile inside the builder phone preview](https://iili.io/CwBoECB.png)

### Builder configuration

| Setting                 | What it does                    | Recommended default                     |
| ----------------------- | ------------------------------- | --------------------------------------- |
| Empty state title       | Fallback heading                | `Your profile`                          |
| Empty state description | Explains prefs purpose          | Mentions landing screen + notifications |
| Empty action label      | Associated with save affordance | `Save`                                  |

{% hint style="success" %}
**Maker tip**\
Mark the screens you want as landing candidates as primary in navigation. Profile only lists primary screens for the default landing picker.
{% endhint %}

### Mental model

```
Profile = per-user prefs (landing + notifications) + logout
```

| Layer   | Profile meaning                                    |
| ------- | -------------------------------------------------- |
| Builder | Empty-state copy                                   |
| APIs    | GET/PATCH end-user prefs for the app               |
| Live UX | Landing picker, notification toggles, save, logout |

### How landing screen works

1. User opens **Profile**.
2. Selects a primary screen under **Default landing screen**.
3. Taps **Save preferences**.
4. On next launch (or after prefs boot), the app opens that screen when allowed.

If no preference is saved, the app uses its normal navigation default (often the first primary screen).

### Testing checklist

* [ ] Profile lists the expected primary screens
* [ ] Selecting a landing screen + Save persists after reload
* [ ] In-app / email toggles save correctly
* [ ] Log out returns the user to the signed-out experience
* [ ] Phone layout keeps Save and Log out reachable

### Troubleshooting

| Symptom                    | Likely cause                        | What to check                                 |
| -------------------------- | ----------------------------------- | --------------------------------------------- |
| Landing list empty         | No primary screens                  | Mark screens primary in **Edit Navigation**   |
| Prefs do not stick         | Save not tapped, or prefs API error | Tap **Save preferences**; retry after publish |
| User still lands elsewhere | Visibility hides the chosen screen  | Confirm the user can see that screen          |
| Logout missing / broken    | Auth host / private app setup       | Confirm private app login works end-to-end    |

### Best practices

* Always add Profile to private apps
* Put it in a predictable place (last tab / More)
* Tell users in Home empty copy that they can change landing in Profile