Skip to content
Thalovant Thalovant Thalovant Docs
Thalovant logo mark.

Thalovant Help

Find the right path to learn Thalovant, finish your first setup, or fix the thing that looks wrong.
Start with the basics See how it works Choose next step

How Can We Help?

Section titled “How Can We Help?”
If you came here to…Start with
Learn the basicsQuick Start
Finish one setupFirst Successful Setup
Fix a visible problemTroubleshooting Decision Tree
Choose the next pageWhat Should I Do?
I am new Learn the few words you need before creating anything.
I want my first setup Complete one hub, one client, one permission set, and one health check.
A button is locked Check whether the action is blocked by plan limits or workspace usage.
My client is offline Review client state, hub choice, connection file placement, and last update.
Access is wrong Fix access that is too wide, too narrow, denied, or hard to review.
Live Map is stale Understand stale, missing, not showing, and warning states.
Language or voice is wrong Check runtime settings for language, location, speech, time zone, and blocked skills.
I still need help Collect the right details before asking for support.

Learning or Fixing

Section titled “Learning or Fixing”
Learn Thalovant Follow a five-, fifteen-, and thirty-minute path from zero context to one healthy setup.
Fix a problem Start with the visible symptom and choose the next page to check.
Section titled “Popular Topics”
Getting started Learn workspace, hub, client, permissions, skills, runtime, Dashboard, and Live Map.
Clients and connection files Create clients, keep connection files private, and fix offline clients.
Permissions Keep access narrow, readable, and tied to one client purpose.
Billing and locked actions Understand limits, paid features, hub addresses, and upgrade required messages.
Runtime settings Review language, location, speech, time zone, blocked skills, and live skill status.
Live Map troubleshooting Use connected, stale, missing, and warning states to find the next check.

If You Are Brand New

Section titled “If You Are Brand New”

You do not need to know any Thalovant words before using these docs. Start with this simple idea:

A hub is the place to connect to. A client is what connects. Permissions decide what the client can do.

That is enough to begin. Runtime, skills, Billing, Dashboard, and Live Map become easier after you understand that first relationship.

Use this order if you are starting from zero:

  1. Read Quick Start. Learn the few words used across the product.
  2. Read How Thalovant Works. See how workspace, hub, client, permissions, skills, and runtime fit together.
  3. Choose one route. Use What Should I Do? to pick public hub, owned hub, client setup, permissions, or troubleshooting.
  4. Create one complete loop. Finish one hub, one client, one permission set, and one health check before adding more.

Task Paths

Section titled “Task Paths”
Create your first setup Finish one safe loop before adding more.
Create a hub Create a private or public destination for clients.
Connect a client Create the app, device, or experience that connects to a hub.
Set permissions Control what a client can do on a hub.
Fix a locked action Check whether the plan or current usage blocks the action.
Fix a stale client Use Live Map and Clients to find missing or old live updates.
Review runtime settings Check language, location, speech, time zone, and blocked skills.
Try a public hub Browse shared hubs, create a client, and keep access narrow.

The Simple Version

Section titled “The Simple Version”

Thalovant starts with your workspace. Your plan decides what the workspace can create. A hub is the place an app or device connects to. A client is the app or device you connect. Permissions decide what that client is allowed to do. Skills give a hub useful abilities, and runtime holds the shared settings behind those skills.

For the fuller explanation, read How Thalovant Works.

Thalovant Dashboard overview showing plan, hubs, clients, items that need attention, and updates.
Dashboard is the first place to check what you have, what is healthy, and what needs attention.

Hub

A hub is the place an app or device connects to. It can be private for your workspace or public for others to find.

Runtime

Runtime is the working setup behind a skill set. It keeps shared defaults like language, location, speech settings, and live skill status.

Client

A client is the app, device, or experience that connects to a hub. Give each client a clear name so you can recognize it later.

Permissions

Permissions say what a client can and cannot do on a hub.

How a First Setup Works

Section titled “How a First Setup Works”

Most first setups follow the same simple path:

  1. Check your plan. Billing explains what your workspace can create.
  2. Choose or create a hub. This is where the client will connect.
  3. Choose the skills. Skills give the hub its abilities.
  4. Review runtime only when needed. Runtime config sets shared language, location, speech, and blocked-skill defaults.
  5. Create a client. This is the app, device, or experience that connects.
  6. Set permissions. Keep access simple and only allow what the client needs.
  7. Check status. Dashboard gives the overview. Live Map shows connected, stale, or missing clients.

Stop after the first complete setup and verify it. Adding a second hub or client is much easier after the first loop is healthy.

For a guided version of these steps, use First Successful Setup.

High-Quality Setup Habits

Section titled “High-Quality Setup Habits”

Check limits before setup

Billing keeps plan limits, private skill setups, hub addresses, paid skills, and help options visible.

Change shared defaults deliberately

Use separate skill sets when only one hub should receive different runtime behavior.

Keep permissions narrow

Let each client do only what its name and purpose explain.

Healthy Setup Checklist

Section titled “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.
Setup flow from workspace plan to hub, skills, client, permissions, Dashboard, and Live Map.
The simple flow: your plan sets limits, the hub receives the connection, the client connects, and permissions decide what is allowed.

What You Can Do

Section titled “What You Can Do”
Dashboard See your workspace summary, health, attention items, and updates.
Public hubs Try shared hubs and create a first client without creating your own hub.
Hubs Create or review the places clients connect to.
Runtime Review the shared settings behind a skill set.
Skills Add, update, configure, or review the abilities available to a hub.
Clients Connect an app or device and get its connection file.
Permissions Decide what each client can do.
Scenario playbook See named examples for public hubs, private hubs, access reviews, stale clients, and runtime changes.

Setup Flow

Section titled “Setup Flow”
flowchart LR
  Workspace((Workspace)) --> Plan[Billing / plan]
  Plan --> 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 --> Dashboard[Dashboard]
  Hub --> LiveMap[Live Map]
  Client --> LiveMap
  Public[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 Plan,Runtime,RuntimeConfig,SkillSet,SetupFile,Public support
Section titled “Recommended Reading Order”
  1. Start with the quick start. Learn the few words you will see everywhere.
  2. Use the learning path. Follow the five-, fifteen-, and thirty-minute route if you want a guided order.
  3. See how Thalovant works. Use the simple model before creating anything.
  4. Create one first setup. Use First Successful Setup for one hub, one client, one permission set, and one health check.
  5. Choose a path. Decide whether to try a public hub, create your own hub, or prepare a team workspace.
  6. Understand runtime. Learn when to keep the default and when a separate skill set needs its own runtime config.
  7. Check status. Use Dashboard and Live Map to see what is healthy and what needs attention.