Observer
Best when a client only needs to check status.
Clients
A client is the app, device, or experience that connects to a hub.
Clients are not just names in a list. A client is connected to one hub, has a private connection file, and has permissions.
Give each client a clear name so you can recognize it later in Dashboard, Permissions, and Live Map.
Before creating a client, choose the hub it should connect to. After creation, review permissions and Live Map so the setup is easy to verify.
Start Here If
Section titled “Start Here If”- the client is offline or not connected;
- you cannot connect an app or device;
- 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
Section titled “At a Glance”| Question | Simple answer |
|---|---|
| What is a client? | The app, device, or experience that connects. |
| What does it connect to? | One hub. |
| What file does it use? | A private connection file. |
| What limits it? | Permissions. |
| Where do I check it? | Clients first, then Dashboard and Live Map. |
Client Types
Section titled “Client Types”Question client
Best when a user-facing experience should ask normal questions.
Skill helper
Best when Thalovant needs help seeing which skills are available for permissions.
Create a Client
Section titled “Create a Client”Before creating a client, choose the hub it should connect to and decide what the client is for.
- Open Clients. Select Create client.
- Choose a hub. Attach the client to the hub it should use.
- Name the client. Use a name that describes the app, device, or purpose.
- Choose a type. Start with observer, question client, or skill helper.
- Keep wide controls off. Leave wider message sending, higher-level requests, passing work along, and full-control access off unless the client clearly needs them.
- Get the connection file. Place it only where the app or device needs it.
Do not create several clients just to test names. Create one client, connect it, give it narrow permissions, and confirm it appears where expected.
Choose the Right Behavior
Section titled “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. |
Connection Files
Section titled “Connection Files”After creating a client, Thalovant can provide a private connection file. The app or device uses this file to connect.
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.
Client vs Connection File
Section titled “Client vs Connection File”The client is what you manage in Thalovant. The connection file is what the app or device uses outside Thalovant to connect.
If a connection file is lost or exposed, do not just rename the client. Pause, lock, or recreate the client so the old file can no longer be used.
Access and Control
Section titled “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
Section titled “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
Section titled “Presence and State”The Clients 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:
- get the private connection file;
- 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
Section titled “If the Client Is Not Live”Some teams describe this as client offline, client not connected, can’t connect, 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, connection file, and live state.
Check these in order:
- Client: confirm it is active and attached to the expected hub.
- Connection file: confirm the app or device has the current private file.
- Permissions: confirm the client can do what it needs on the hub.
- Live Map: check whether the client is connected, stale, missing, or warning.
Client Is Ready When
Section titled “Client Is Ready When”A client is ready when:
- its name explains the app, device, or purpose;
- it is attached to the intended hub;
- 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.