How Thalovant Works
Use this page when the product words still feel mixed together.
The whole model is small:
A hub is where a client connects. Permissions decide what that client can do.
The Words
Section titled “The Words”| Word | Meaning |
|---|---|
| Workspace | Your Thalovant account area. |
| Hub | The place a client connects to. |
| Client | The app, device, voice room, browser flow, or agent that connects. |
| Permissions | The access a client has on a hub. |
| Skills | What a hub can do. |
| Runtime | Shared settings for skills, such as language, location, and speech. |
| Dashboard | The workspace health summary. |
| Live Map | The live view of hubs and clients. |
The Setup Order
Section titled “The Setup Order”The order matters because later choices depend on earlier ones:
- Plan first: you need to know what the workspace can create.
- Hub second: the client needs a destination.
- Connection third: permissions are easier to read when the client already exists.
- Permissions fourth: access should match the client purpose.
- Dashboard and Live Map last: verification tells you whether the setup is healthy.
Where to Look
Section titled “Where to Look”| Item | Question it answers | Healthy sign |
|---|---|---|
| Billing | What does my plan allow? | The plan shows room for the thing you want to create. |
| Hub | Where does the client connect? | The hub is ready and is set as public or private as expected. |
| Connection | What app, device, or browser flow is connecting? | The client is active, clearly named, and attached to the right hub. |
| Permissions | What is allowed? | The client is allowed to do only what it needs. |
| Dashboard | What needs attention? | The summary and alerts match what you expect. |
| Live Map | What is connected now? | Connected, stale, and missing clients are easy to spot. |
The Healthy Loop
Section titled “The Healthy Loop”Use this loop whenever you are unsure where a problem belongs:
- Start with Billing when a button is unavailable or you cannot create something.
- Open Hubs when the place to connect is the question.
- Open Connections when an app, device, or agent is missing or stale.
- Open Permissions when access is wrong.
- Open Dashboard for the workspace summary.
- Open Live Map to see what is connected now.
When to Split Things
Section titled “When to Split Things”Create a separate hub when you need a different place to connect to, a different public/private setting, or different skills.
Create a separate connection when a different app, device, or purpose needs its own setup.
Create separate permissions when two clients should not be allowed to do the same things.
Change skills or runtime only when the default setup cannot do what the hub needs.
Next Step
Section titled “Next Step”After this feels clear, set up one client.
Build the first setup