What Should I Do?

Use this page when you know the outcome you want, but you are not sure which page to open first.

If you are still learning the words, start with Quick Start first. This page works best after you can recognize hub, client, and permissions.

Start Here If

Use this page when:

• you know the job but not the first docs page;
• a button, client, permission, hub, or Live Map state is sending you in circles;
• you need to choose between public discovery and an owned hub;
• you want one next page instead of a full tour.

Choose the route that matches the next job, then verify it with Dashboard and Live Map.

Start With Your Goal

Try an existing hub Start with public discovery, create one client, and keep access narrow.

Create my own hub Check your plan, create one hub, choose skills, and connect one client.

Finish the first setup Use a guided loop for one hub, one client, permissions, and health checks.

Connect an app or device Create a client, choose the hub, and keep the connection file private.

Control what a client can do Create narrow permissions for one client and one hub.

Understand a blocked action Check whether the plan allows the thing you are trying to create.

Fix a stale or missing client Use Live Map, then check the client, connection file, and permissions.

Decision Map

flowchart LR
  Goal((Goal)) --> Choice{What are you trying to do?}
  Choice -->|Try first| Public[Public hubs]
  Choice -->|Own the setup| Billing[Billing]
  Choice -->|Connect something| Client[Clients]
  Choice -->|Control access| Rules[Permissions]
  Choice -->|Check health| LiveMap[Live Map]
  Billing --> Hub[Create a hub]
  Hub --> Skills[Skills]
  Skills --> Runtime[Runtime]
  Public --> Client
  Client --> Rules
  Rules --> Check[Dashboard]
  LiveMap --> Client
  Check --> LiveMap

  classDef start fill:#171d25,stroke:#818dd1,color:#e8edf5,stroke-width:2px
  classDef decision fill:#211b2c,stroke:#d37784,color:#e8edf5,stroke-width:2px
  classDef setup fill:#141d2c,stroke:#6170c0,color:#e8edf5,stroke-width:2px
  classDef verify fill:#10251f,stroke:#2ea47f,color:#e8edf5,stroke-width:2px
  class Goal start
  class Choice decision
  class Public,Billing,Hub,Skills,Runtime,Client,Rules setup
  class Check,LiveMap verify

Choose a Route

I am exploring

1. Open Public hubs.
2. Pick a hub with clear tags and starter prompts.
3. Create one client.
4. Keep permissions narrow.
5. Check Dashboard.

I need my own hub

1. Open Billing and confirm the plan allows the hub and client.
2. Create the hub with a clear name.
3. Use the default skills unless the hub needs something different.
4. Create one client.
5. Set permissions, then check Dashboard and Live Map.

I need a team setup

1. Agree on names for hubs, clients, and permissions.
2. Decide who reviews wider access.
3. Decide when runtime settings can change.
4. Create one complete hub-client-permissions loop.
5. Repeat only after the first loop is healthy.

Something looks wrong

1. Start with Dashboard to see the visible warning.
2. Use Live Map when the issue is a stale or missing client.
3. Open Clients when the connection file, pause state, or hub choice may be wrong.
4. Open Permissions when the client exists but access is unexpected.
5. Open Billing when a button is unavailable or a limit is reached.

Use One Route at a Time

Choose the route that matches the next job in front of you. Finish that route, check Dashboard, then decide whether you need another route.

If you are thinking…	Start with
”I just want to try it.”	Public hubs
”I need my own destination.”	Create a hub
”I have an app or device to connect.”	Clients
”Access looks too wide or too narrow.”	Permissions
”Something disappeared or stopped updating.”	Live Map, then Clients
”A button is locked.”	Billing

Healthy Setup Checklist

1. One clear hub. The hub name says what it is for.
2. One clear client. The client name says what app, device, or experience connects.
3. Narrow permissions. The client can do only what it needs.
4. Simple runtime settings. Keep the default unless language, location, speech, or blocked skills need to change.
5. Dashboard looks expected. Counts and attention items match what you created.
6. Live Map looks expected. The client appears when live status is available.

Tip

Thalovant is easiest to learn with one complete loop first: one hub, one client, one permission set, and one health check.

Next Best Page

After choosing a route, use the scenario playbook to see the same pattern with realistic names.

Open scenario playbook