Clients and Connections

A client is the app, device, or experience that connects to a hub. In the product, you manage clients from Connections.

Clients are not just names in a list. A client is connected to one hub, has a setup path, and has permissions.

Give each connection a clear name so you can recognize it later in Dashboard, Permissions, and Live Map.

Before creating a connection, choose the hub it should use. After creation, review permissions and Live Map so the setup is easy to verify.

Start Here If

• the client is offline or not connected;
• you cannot connect an app, device, browser flow, or Thalovant Voice;
• the setup link expired or did not open the client;
• the connection file is missing, old, exposed, or called a config file by your team;
• a client disappeared from Live Map or is not showing where you expected;
• you need to know whether to pause, lock, restore, or recreate a client.

At a Glance

Question	Simple answer
What is a client?	The app, device, browser flow, or experience that connects.
Where do I manage it?	Connections.
What does it connect to?	One hub.
What does first setup use?	A secure one-time setup link.
What file can still matter?	A private connection file for advanced or recovery paths.
What limits it?	Permissions.
Where do I check it?	Clients first, then Dashboard and Live Map.

Clients are what connect to a hub. Permissions decide what each client may do there.

Connection Types

Voice client

Best for rooms, kiosks, and assistants that listen and speak with Thalovant Voice.

Web chat

Best for browser conversations without installing a desktop app.

Developer client

Best for CLI, API, diagnostics, automation, or local testing.

Embedded client

Best for hardware, firmware, and small-device provisioning.

Create a Connection

Before creating a connection, choose the hub it should use and decide what the client is for.

1. Open Connections. Select Add connection.
2. Choose a type. Pick Voice, Web chat, Developer, or Embedded.
3. Choose a hub. Attach the connection to the hub it should use.
4. Name the connection. Use a name that describes the app, device, room, or purpose.
5. Choose access. Keep the recommended narrow behavior unless the client clearly needs more.
6. Open setup. Use the one-time setup link so the client can claim its identity.

Do not create several clients just to test names. Create one connection, pair it, give it narrow permissions, and confirm it appears where expected.

For a guided task flow, use Connect a Client.

Choose the Right Behavior

Type	Best for	Permission style
Observer	Clients that only need to check status.	Read-only access.
Question client	User-facing experiences that ask normal questions.	Questions allowed, wider control blocked.
Skill helper	Clients that help Thalovant see available skills.	Skill sharing plus only the small reads it needs.

Setup Links

After creating a connection, Thalovant prepares a setup link. That link can be used once and expires.

For Thalovant Voice, the setup page can download the app, open it, and wait for the first heartbeat. On Linux, it can copy a single command that installs, pairs, and starts the voice runtime.

For Web chat, Developer, and Embedded connections, open or copy the setup link into the target client or provisioning tool.

If a setup link expires, is shared, or was already used, create a new setup link from the connection actions.

Connection Files

Most first setups should use the setup link. Some developer, embedded, or recovery paths may still need a private connection file.

If you are asking “where is my config file?”, start with the client record. Some teams say config file when they mean the private connection file.

For security, Thalovant may ask for two-step sign-in or a recovery code before showing the file. First-time setup may offer the file right away so you can finish connecting the client.

Keep setup material private

Treat setup links, copied setup commands, and private connection files like passwords. Store them only where the client needs them, and recreate the connection if they are exposed.

Client vs Setup Material

The client is what you manage in Thalovant. The setup link or connection file is what the app, device, or tool uses to pair.

If setup material is lost or exposed, do not just rename the client. Create a new setup link, or pause, lock, or recreate the client when a private file may have been exposed.

Access and Control

Client settings can allow broader actions:

• Broadcast lets the client send wider messages.
• Escalate lets it ask for higher-level actions.
• Propagate lets it pass work along when available.
• Full control gives wide control and should be rare.

Most clients should start simple. Add only the extra powers the client truly needs.

Naming Clients Well

Good client names describe purpose or location, not just a person. Names like frontdesk-client, skill-sync, or kiosk-reader are easier to recognize than test-1 or main.

When a client shows stale or warning state later, a clear name helps you know which app, device, or service needs attention.

Presence and State

The Connections page shows status, type, permissions, and last activity. A live dot means the client is connected now. Stale or missing means Thalovant has not received a fresh update for that client.

Useful actions include:

• create a setup link;
• get the private connection file when that path is needed;
• edit type and hub choice;
• pause or restore access;
• lock or unlock access when permitted;
• remove the client when it is no longer needed.

If the Client Is Not Live

Some teams describe this as client offline, client not connected, can’t connect, setup link expired, client missing, client disappeared, config file missing, or connection file missing. Start with the client record before changing the hub.

If the person says the device is gone or device gone, still start here. A device usually maps back to a client record, setup link or connection file, and live state.

Check these in order:

1. Client: confirm it is active and attached to the expected hub.
2. Setup: create a fresh setup link if the link expired, was used, or was shared.
3. Connection file: confirm the app or device has the current private file if that path is used.
4. Permissions: confirm the client can do what it needs on the hub.
5. Live Map: check whether the client is connected, stale, missing, or warning.

Client Is Ready When

A client is ready when:

• its name explains the app, device, or purpose;
• it is attached to the intended hub;
• setup was claimed by the intended client, or the connection file is stored only where the client needs it;
• permissions match the client purpose;
• Dashboard and Live Map show the expected state when live status is available.