Routes by Responsibility

Use this page when several people share a workspace and each person needs a different reading path. Pick the responsibility closest to your current job, then follow the linked pages in order.

If one person has several responsibilities, finish the shortest route first. The docs work best when each setup change has one clear goal.

Start Here If

• different teammates own plan, setup, access, health, or support questions;
• you need to hand someone one route instead of the whole docs set;
• a support handoff needs the first owner page;
• the team wants shared language for who checks what.

Pick Your Responsibility

New readerLearn the main words and the first hub-connection-permissions loop.

First setup builderCreate one hub, one connection, one permission set, and one health check.

Plan reviewerConfirm limits, locked actions, paid access, addresses, and help options.

Access reviewerCheck whether each client can do only what it should do.

Health reviewerUse Dashboard and Live Map to understand missing, stale, or warning states.

Support contactTurn a visible symptom into the next page to check.

Route Summary

Responsibility	Read first	Then read	Stop when
New reader	Quick Start	Learning Path	You can explain hub, client, and permissions.
First setup builder	First Successful Setup	Scenario Playbook	One setup passes Dashboard and Live Map checks.
Plan reviewer	Billing	Public Hubs	You know whether a locked action is a plan limit.
Access reviewer	Permissions	Clients	Each client has a readable purpose and narrow access.
Health reviewer	Dashboard	Live Map	The visible status points to one likely owner page.
Support contact	Decision Tree	Troubleshooting Index	You can report the item name, status, page, and last check.

Team Reading Plan

One person

1. Read Quick Start.
2. Complete First Successful Setup.
3. Use the scenario playbook for the closest real example.
4. Keep the Troubleshooting Index open while checking Dashboard and Live Map.

Small team

1. Agree on hub, client, and permission names before creating items.
2. Have one person own the first setup loop.
3. Have one person review plan limits and locked actions.
4. Have one person review permissions after the first connection exists.

Support handoff

1. Start from the visible symptom, not guesses.
2. Capture the page name, item name, status text, and last refresh time.
3. Use the Decision Tree to choose the next page.
4. Avoid changing multiple settings before the next check.

Naming Agreement

Good shared docs depend on good shared names. Before creating more items, agree on:

• a hub naming pattern;
• a client naming pattern;
• a permissions naming pattern;
• who reviews broader access;
• when runtime settings can change;
• where to record plan decisions.

Done When

Your route is done when the next reader knows exactly which page to open, what question that page answers, and what result would count as healthy.

1. Name the responsibility. This keeps the route focused.
2. Open the first linked page. Avoid jumping between unrelated areas.
3. Finish one route. Verify the result before adding a second responsibility.
4. Record any unclear term. Add it to the glossary or link to the page that defines it.