First Setup

Use this page when you want the first setup to work before learning every feature.

By the end, you should have one hub, one client, one permission set, and one health check that all agree.

Before You Start

• You can sign in to the workspace.
• You know whether you want a public hub or your own hub.
• You know what app, device, room client, or agent will connect.
• You have a few minutes to check the result.

If a create button is locked, open Billing before changing the setup. Plan limits are different from setup problems.

1. Choose the Hub

Start with the smallest choice that fits your goal.

Goal	Best first hub choice
Try Thalovant without owning a hub	Use Public hubs.
Build a private or team-controlled setup	Create one hub with Create a hub.
Learn the model before creating anything	Read How Thalovant Works.

Use a name that explains the purpose. support-frontdesk is better than test.

2. Keep Skills Simple

Use the default skills unless the hub needs something different today.

Runtime settings can wait. Change them later only when language, location, speech, or blocked skills need to be different for this hub.

3. Create One Connection

Create one connection for the app, device, browser flow, or Thalovant Voice client that will connect to the hub.

1. Open Connections. Choose Add connection.
2. Choose the connection type. Voice is best for Thalovant Voice, rooms, kiosks, and assistants.
3. Attach it to the chosen hub. Avoid creating extra connections until this one works.
4. Name the connection by purpose. Use a name like frontdesk-voice or demo-chat.
5. Use the setup link. Let the client claim its identity once.
6. Keep setup material private. Do not share setup links or connection files.

Read Connect a Client for the full pairing flow.

4. Add Narrow Permissions

Permissions should describe what the client is allowed to do on the hub.

Use a name that explains the purpose, such as:

• frontdesk-questions-only;
• demo-read-only;
• skill-status-read;
• temporary-review-window.

Ask:

• Does the name match the client purpose?
• Are allowed actions specific?
• Is anything broader than needed blocked?
• Would a teammate understand this access?

Read Permissions before adding broader access.

5. Check Dashboard

Open Dashboard and check the Fleet overview.

The Dashboard should answer:

• did the expected hub count change?
• did the expected client count change?
• is there an attention item that names this setup?
• does the visible status match what you expected?

Do not continue adding more items until the Dashboard view makes sense.

6. Check Live Map

Open Live Map when live status is available.

Look for:

• the hub you chose;
• the client you created;
• a connected, stale, missing, or warning state;
• a route from the visible symptom back to Clients, Permissions, Runtime, or Billing.

If the client is missing or stale, check Clients first. If the client exists but access is unexpected, check Permissions next.

Done When

The first setup is done when:

• the hub has a clear purpose;
• the connection name explains what connects;
• the setup link was claimed by the intended client;
• any connection file is private;
• permissions are narrow and readable;
• Dashboard shows the expected counts or attention item;
• Live Map matches the real connection state when it is available.

Tip

Stop after the first healthy loop. A second hub or connection is easier once the first one is trusted.

Next

Create another connection only if the first one is healthy.

Connect another client