> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Team Home for Auto-dispatch
> Use Team Home in Inbox to see read-only Insights for a team's Views and a live Members table with dispatch presence, capacity, and availability toggles.
Team Home is part of the **Auto-dispatch Partner Beta**. Contact your Thread representative if you'd like to join the beta.
Team Home is a per-team page in Inbox that gives Admins and Team Admins a live view of dispatch activity for a single team. It has two sections stacked on the page:
* **Insights** — the same slice charts and tables you get from a View's Insights panel, scoped to one of the team's Views. Read-only, so nothing you click reassigns or reroutes a thread.
* **Members** — the team roster with live auto-dispatch data overlaid on it: presence dots, active-thread counts, and per-member availability toggles you can flip on someone's behalf.
Team members (non-admin roles) don't see Team Home — the page is only visible to **Admins** and **Team Admins**.
## Who sees Team Home
| Role | Team Home visible? |
| ---------- | ------------------ |
| Admin | Yes |
| Team Admin | Yes |
| Member | No |
Team Admin scope is set per team. See [Team Admin role](/inbox/team-admin-role).
## Open Team Home
In Inbox, expand the team in the left rail whose home page you want to view.
Select **Home** under the team name. Team Home opens with the **Insights** panel at the top and the **Members** table below it.
## Insights
The Insights panel on Team Home is the same one that lives inside a View — the same slice set (Priority, Status, Owner, Company, Create Date, plus Sentiment and XLA where enabled), the same first-page-of-200 thread limit, the same charts and tables. The differences are:
* **It's scoped to one of the team's Views.** Use the **View** picker in the panel header to switch between any View that belongs to the team. The picker shows the thread count for the current View next to its name.
* **Slice with the Slice picker.** Pick a dimension from the **Slice** dropdown to change the chart. Team Home defaults to **Priority**.
* **It's read-only.** Clicking a bar, segment, or row on Team Home doesn't drill into the underlying threads or change what the View shows. Open the View itself if you want to drill in and act on threads.
If the team doesn't have any Views yet, the Insights panel shows a **Create team view** button that seeds a new View pre-scoped to the team. See [Views and Insights](/inbox/views-and-insights) for how Views and slices work.
## Members
The Members table lists every active member of the team, with a role badge, a search box, and — for teams in an active auto-dispatch profile — dispatch data on each row.
What appears in the columns depends on the team's dispatch mode.
### Auto-assign (push) teams
For teams whose profile uses **Auto-assign**, the Members table adds:
* **Presence dot** on each avatar — green if the member is available for this team's dispatch, grey if offline. This is the same presence signal you see next to avatars in the left rail.
* **Active threads** — the member's current active count over the profile's Max threads limit (for example, `3 / 10`). The active count is **semibold**, and turns **red** when the member is at or over capacity. The math matches the push dispatcher exactly, so the number you see here is the number Auto-assign is using to decide who gets the next thread.
* **Available** — a toggle you can flip on the member's behalf to make them available or unavailable for Auto-assign. See [Who can toggle another member's availability](#who-can-toggle-another-members-availability) for the rules.
* **Excluded members** render faded, with the toggle disabled and an **Excluded from auto-dispatch** tooltip on hover. Excluded members are set in the profile — see [Auto-dispatch profiles](/inbox/auto-dispatch-profiles).
### Next thread (pull) teams
For teams whose profile uses **Next thread** (self-serve), the Members table shows a single dispatch column:
* **Pulled last 24h** — how many threads each technician has pulled in the last 24 hours.
Use this to spot who has and hasn't pulled work today, and to sanity-check that scoring is distributing threads the way you expect.
### Sync now
The Members table refreshes automatically every few minutes. A footer under the table shows **Last synced *N* minutes ago** and a **Sync now** button you can hit at any time to refetch immediately. Sync now is disabled while a member's Available toggle is still flipping — a mid-toggle refetch would clobber the optimistic state.
## Who can toggle another member's availability
Flipping the **Available** toggle in the Members table changes another member's push-dispatch availability on their behalf. Thread authorizes the change with a **team-manage policy**:
| Role | Can toggle another member's availability? |
| --------------- | ----------------------------------------- |
| Workspace admin | Yes, for any team |
| Team admin | Yes, for teams they team-admin |
| Member | No |
An unauthorized attempt returns a 403 and the toggle snaps back — no availability change is recorded. Members can always toggle **their own** availability from the account menu regardless of role; the Team Home path is only for changing someone else's.
The **Available** toggle in the Members table and the **Available for dispatch** control in each technician's account menu drive the same server-side state. When you flip a row here, Inbox optimistically updates both surfaces and invalidates the caches feeding them, so the technician's own avatar dot and account-menu switch update the next time their client polls. When they flip their own switch, your Members row updates on the next sync. See [Set your availability for auto-dispatch](/inbox/available-for-dispatch) for the account-menu control.
## Teams without an auto-dispatch profile
If the team isn't part of any enabled auto-dispatch profile yet, Team Home still opens, and the Members table still lists the roster — just without the dispatch columns. A dismissible **Get started** banner at the top of the Members section links to the auto-dispatch admin so you can create or attach a profile:
> Let auto-dispatch handle thread assignments for this team. **Get started**
Dismiss the banner from its `×` control if you'd rather run the team without auto-dispatch. It reappears the next time the team is loaded until a profile is attached.
## Action when no tech is eligible
Auto-assign profiles let you choose what happens when a thread is ready to dispatch but no technician is available. You pick the behavior in the profile's **Technician assignment** section, under **Action when no tech is eligible**.
You have two options:
* **Retry assignment** (default) — Auto-assign holds the thread and re-checks every minute. As soon as a tech becomes available, the highest-priority waiting thread is dispatched first; ties are broken by oldest thread. The thread stays in its current status and no internal note is added until a tech is successfully assigned.
* **Apply a status change** — Auto-assign moves the thread to a status you pick per board instead of waiting. Use this if you'd rather have unassigned threads drop into a dispatcher queue than sit in retry.
Retry assignment is the out-of-the-box behavior. You no longer need to configure a fallback status just to turn Auto-assign on.
## FAQ
Either the member is **excluded** from the team's auto-dispatch profile (hover the row for the **Excluded from auto-dispatch** tooltip), or you don't have permission to change their availability. Workspace admins can toggle any member; team admins can toggle only members of teams they team-admin.
The count uses the same capacity math as the push dispatcher — it counts threads assigned to the member that sit in a status the profile counts toward **Max threads**. Statuses outside that set aren't included even if the thread is technically open. See **Technician assignment** in [Auto-dispatch profiles](/inbox/auto-dispatch-profiles).
No — Insights on Team Home is read-only. Open the underlying View (from the left rail or the View picker in the Insights header) to drill into threads and act on them.
Every minute. When a tech becomes available, Auto-assign dispatches the highest-priority, oldest waiting thread first.
Nothing changes on the thread itself. It stays in its current status and Thread does not add an internal note until a tech is successfully assigned.
No. A fallback status is off by default and only applies if you switch **Action when no tech is eligible** to **Apply a status change**. Retry assignment covers the no-available-tech case without one.
## Related topics
- [Set your availability for auto-dispatch](/inbox/available-for-dispatch.md)
- [Assign and schedule](/start-here/roles/dispatcher/assign-and-schedule.md)
- [Dispatcher](/start-here/roles/dispatcher.md)