How Thalovant Works

Use this page when the words are still new. Thalovant is easiest to understand as a short story about where something connects, what is connecting, and what it is allowed to do.

Start Here If

Use this page when:

• workspace, hub, client, permissions, skills, or runtime still feel mixed together;
• you want the product model before creating anything;
• a teammate needs a plain-language explanation of the setup order;
• you need to decide which owner page should answer a question.

The Short Version

Thalovant starts with your workspace. This is your account area.

Inside the workspace, your plan decides what you can create. Runtime is the working setup behind a skill set. A hub is a place to connect to. A client is the app, device, or experience that connects. Permissions decide what that client can do. The client also gets a private connection file that helps it connect.

Dashboard tells you how the workspace is doing. Live Map shows which clients are connected, stale, or missing.

One-Sentence Model

If you remember only one sentence, use this:

A workspace contains hubs; clients connect to hubs; permissions keep each client limited to the work it should do.

Skills and runtime explain what the hub can do and which shared defaults those abilities use.

The core model is a small chain: plan, hub, skills, client, permissions, then health checks.

System Map

flowchart TB
  Workspace((Workspace)) --> Billing[Billing and plan]
  Workspace --> Dashboard[Dashboard]
  Workspace --> Profile[Profile and security]
  Billing --> Runtime[Runtime access]
  Workspace --> Hub[Hub]
  Runtime --> SkillSet[Skills]
  SkillSet --> RuntimeConfig[Runtime config]
  SkillSet --> Hub
  Hub --> Client[Client]
  Client --> SetupFile[Connection file]
  Client --> Rules[Permissions]
  Rules --> Hub
  Hub --> LiveMap[Live Map]
  Client --> LiveMap
  PublicHubs[Public hubs] --> Client

  classDef anchor fill:#171d25,stroke:#818dd1,color:#e8edf5,stroke-width:2px
  classDef rules fill:#211b2c,stroke:#d37784,color:#e8edf5,stroke-width:2px
  classDef live fill:#10251f,stroke:#2ea47f,color:#e8edf5,stroke-width:2px
  classDef support fill:#141d2c,stroke:#6170c0,color:#e8edf5,stroke-width:2px
  class Workspace,Hub,Client anchor
  class Rules rules
  class Dashboard,LiveMap live
  class Billing,Runtime,RuntimeConfig,Profile,SkillSet,SetupFile,PublicHubs support

The Layers

Workspace

Your account area. It includes your plan, security settings, and the hubs and clients you use.

Hub

The place a client connects to. A hub can be private or public.

Runtime

The shared working setup behind a skill set. It keeps language, location, speech, and live skill defaults.

Client

The app, device, or experience that connects to one hub.

Permissions

Says what the client can do on the hub.

Why the Order Matters

The order matters because later choices depend on earlier ones:

1. Plan first: you need to know what the workspace can create.
2. Hub second: the client needs a destination.
3. Client third: permissions are easier to read when the client already exists.
4. Permissions fourth: access should match the client purpose.
5. Dashboard and Live Map last: verification tells you whether the setup is healthy.

How to Read Any Item

Most parts of Thalovant answer one simple question.

Item	Question it answers	Healthy sign
Billing	What does my plan allow?	The plan shows room for the thing you want to create.
Runtime	What shared settings do skills use?	The runtime uses the expected language, location, speech, and blocked-skill defaults.
Hub	Where does the client connect?	The hub is ready and is set as public or private as expected.
Skills	What can the hub do?	The right skills are attached to the hub.
Client	What app or device 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

Use this loop whenever you are unsure where a problem belongs:

1. Start with Billing when a button is unavailable or you cannot create something.
2. Open Runtime when skills need different language, location, speech, or blocked-skill defaults.
3. Open Hubs when the place to connect is the question.
4. Open Clients when an app or device is stale, paused, missing, or needs a connection file.
5. Open Permissions when a client can do too much, too little, or the access is unclear.
6. Open Dashboard for the workspace summary.
7. Open Live Map to see what is connected now.

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 client 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.

Create separate skills when one hub needs different abilities.

Create a separate runtime setup when one hub needs different language, location, speech, or blocked-skill defaults.

Next Step

After this feels clear, use What Should I Do? to choose the next page.

Choose the next step