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

# Overview

> The mobile app your residents use to see their own schedule

Puffin for residents is the mobile app for the people *on* your schedule. Once you publish a schedule and enable it in the app, each resident sees their own rotations and shifts as a calendar on their phone, without opening the dashboard.

It works alongside the platform. You build, publish, and enable the schedule on the web. Residents read theirs in the app.

<Frame>
  <img src="https://mintcdn.com/standardforminc-0b00c00f/caUvwi8NfRockUK8/images/puffin_resident_app.png?fit=max&auto=format&n=caUvwi8NfRockUK8&q=85&s=b31cc0a28e9741256a9471024f9e9b37" alt="The Puffin resident app on a phone, showing one resident's own shifts as a color-coded calendar" width="1179" height="2556" data-path="images/puffin_resident_app.png" />
</Frame>

<Note>
  This is a different thing from **Puffin**, the [scheduling assistant](/puffin/overview) inside the dashboard, and from a [published share link](/view-your-schedule/publish), which is a read-only web page. The resident app shows each person their *own* calendar, signed in.
</Note>

## What residents can do

<CardGroup cols={2}>
  <Card title="See their schedule as a calendar" icon="calendar">
    Their assignments appear as day, week, and month views, color-coded by rotation. They swipe between dates and tap any shift for details.
  </Card>

  <Card title="Add personal events" icon="plus">
    Residents can add their own events alongside their shifts, like study time, appointments, or reminders, and edit or delete them.
  </Card>

  <Card title="View in any timezone" icon="globe">
    Times follow the schedule's timezone by default. A resident who travels can switch the display timezone and every shift moves with it.
  </Card>

  <Card title="Sign in securely" icon="lock">
    Each resident signs in with Apple or a one-time email code, then links to their record once with a code you provide.
  </Card>
</CardGroup>

## How residents get on the app

There are two halves, one on your side and one on theirs.

<CardGroup cols={2}>
  <Card title="You: set up and enable" icon="toggle-on" href="/puffin-for-residents/set-up-for-the-app">
    Put residents on the schedule, publish it, and switch on **Enable in app** so their calendars fill in.
  </Card>

  <Card title="They: sign in and link" icon="link" href="/puffin-for-residents/inviting-residents">
    Each resident signs in and enters a single-use link code once to connect the app to their record.
  </Card>
</CardGroup>

Order doesn't matter much. A resident who links after you've enabled the app sees their calendar right away. If you enable the app later, everyone who's linked gets their shifts on the next publish.

## Good to know

* **Residents only see their own calendar.** The app shows the signed-in resident's assignments, not the whole team's grid.
* **Republish keeps it current.** When the app is on, republishing pushes your latest changes to every linked resident automatically. There's no separate step.
* **Editing a shift is local.** A resident can drag or rename a shift, but the schedule details (title, start, end) are restored from the program the next time you republish. Personal touches like color and notes stick.
* **Leave and swaps still run through you.** Submitting leave requests or swaps from inside the app isn't available yet. Those stay on the dashboard for now.