Quick Start

Use this page first if Thalovant is new to you. It explains the small set of words you need before creating anything.

Thalovant is easiest to learn if you start with the three words you will see everywhere:

• Hubs are places to connect to.
• Clients are the apps, devices, or experiences that connect to hubs.
• Permissions decide what each client can do.

Your workspace plan controls what you can create and how many items you can have.

Runtime is another important word, but you usually meet it after the basics. It means the shared working setup behind a skill set: language, location, speech defaults, blocked skills, and live skill status.

Start Here If

Use this page when:

• this is your first pass through Thalovant;
• you need the smallest useful vocabulary before setup;
• you are deciding between a public hub and an owned hub;
• you want to know which page owns each common question.

Quick Start introduces the same loop you will use for the first real setup.

What You Will Know After This Page

After this page, you should be able to:

• explain the difference between a hub and a client;
• choose whether to start with a public hub or your own hub;
• find the page that owns a setup, access, plan, or live-status question;
• check whether your first setup is healthy.

Best first read

If the names still feel abstract, read How Thalovant Works before creating anything. If you want a guided order, use Learning Path. If you already know your goal, jump to What Should I Do?.

The Main Words

Word	Plain meaning	What to check first
Workspace	Your Thalovant account area.	Open Billing to see what your plan allows.
Hub	The place a client connects to.	Decide whether to use a public hub or create your own.
Skills	What the hub can do.	Use the default skills unless you need something different.
Runtime	Shared settings behind a skill set.	Keep the default unless a hub needs different language, location, or speech behavior.
Client	The app, device, or experience that connects.	Choose the hub before getting the connection file.
Permissions	What the client is allowed to do.	Start small and only add what is needed.
Connection file	The private file a client uses to connect.	Keep it private and do not share it in chat or email.
Dashboard	The main health summary.	Start here after signing in.
Live Map	A map of hubs and connected clients.	Use it when something is stale, missing, or not connected.

First Five Minutes

1. Sign in and open Dashboard. Check your workspace summary and any items that need attention.
2. Check Billing. Billing shows what your plan allows.
3. Open Public hubs. If you are just trying Thalovant, start here.
4. Create or review a client. This is the app, device, or experience that will connect.
5. Review permissions. Keep the client limited to what it actually needs.

If you are only exploring, do not create an owned hub yet. Try one public hub, one client, and one narrow permission set first.

Free Path vs Owned Workspace

Free path

Use public hubs, create a simple client, and learn the flow before creating your own hub.

Owned workspace

Create your own hubs, choose skills, use the Live Map, and manage more clients depending on your plan.

Good first route

If you are unsure where to begin, go to Public hubs, choose a hub, then create a client for it. This teaches the core flow without a full private setup.

Need Help Choosing?

Open Learning Path when you want a timed route, or What Should I Do? when you know your goal but are not sure which page should come next.

Follow the learning path Choose the next step

The First Healthy Loop

After your first client exists, read the loop in this order:

1. Client page: confirm the client exists, uses the right hub, and can get its connection file.
2. Permissions page: confirm the client is only allowed to do what it needs.
3. Hub page: confirm the hub lists the client and its permissions.
4. Skills page: confirm the hub uses the expected skill set and runtime defaults.
5. Dashboard: confirm the workspace counts and attention items match what you expect.
6. Live Map: confirm the client appears under the hub when live status is available.

This loop is the fastest way to tell whether the setup is incomplete, permissions are wrong, or the client has not connected yet.

What Not to Worry About Yet

For a first setup, you can usually leave these alone:

• separate skill sets;
• runtime config;
• paid skills;
• custom hub addresses;
• wide permissions.

Come back to those only when the default setup cannot do what your hub needs.

Where Things Live

Need	Go to
Workspace summary, health, updates	Dashboard
Public examples and starter prompts	Public hubs
Owned hub setup, hub addresses, visibility	Hubs
Apps, devices, and connection files	Clients
What clients are allowed to do	Permissions
Hub abilities	Skills
Language, location, speech, and runtime defaults	Runtime
Live hub and client map	Live Map
Two-step sign-in, active browsers, avatar, security	Profile
Plan limits, help, addresses	Billing
Next-step decision	What Should I Do?
Simple examples	Common Patterns
Common setup or connection issue	Common issues

If You Know the Symptom First

If you are thinking…	Start here
”I cannot create a hub.”	Billing
”A button is locked or disabled.”	Billing
”My client is offline or not connected.”	Clients, then Live Map
”The connection file is missing or exposed.”	Clients
”Access is too wide or too narrow.”	Permissions
”Live Map is stale or missing an item.”	Live Map