Known Limits

Use this page when a Thalovant action is locked, unavailable, not showing, or behaving like a boundary rather than a setup failure. If the product says can’t add, start here before changing setup.

Billing is the source of truth for workspace-specific limits. This page explains which limits to check first and how to separate a real product issue from a plan, usage, safety, or live-status boundary.

Start Here If

• a button is locked, disabled, or says upgrade required;
• you cannot create another hub, client, permission set, or private setup;
• a feature appears unavailable even though setup looks correct;
• you need the current Pro owned hub limit;
• a support request needs plan or usage context.

Last reviewed

April 27, 2026. Review this page when plan limits, hub limits, client limits, runtime access, or support options change.

Source of Truth

Limit area	Where to confirm it	What to capture
Current plan	Billing and Plans	Plan name and the message beside the locked action.
Owned hubs	Billing and Plans	Current owned hub usage and limit. Pro allows up to 10 owned hubs.
Clients	Billing and Plans and Clients	Current usage, client state, and whether a connection file exists.
Private skill setups	Billing and Plans and Skill Sets	Whether the plan includes private skill setups.
Runtime config	Runtime	Skill set assignment and runtime setting involved.
Live status	Live Map	Connected, stale, missing, warning, and filter state.
Account security	Profile and Security	Two-step sign-in, recovery codes, and active browser status.

Plan and Usage Limits

Owned hubs

Pro workspaces can have up to 10 owned hubs. If Billing shows 10 of 10, reduce usage or change plan before creating another owned hub.

Clients

Client creation and connection file access can be limited by plan, usage, or account security checks.

Private skill setups

Private skill groups and shared runtime settings depend on the workspace path shown in Billing.

Hub addresses

Custom hub addresses are plan-controlled. Check Billing before treating an address message as a setup failure.

Runtime and Live Limits

Runtime and Live Map issues can look like plan problems when the wrong hub, skill set, or client is being checked.

1. Check Billing first when the product shows locked, disabled, unavailable, upgrade required, or limit reached.
2. Check the owner page next when Billing says the plan allows the action.
3. Check Live Map last when Dashboard, Clients, and Permissions look correct but live state is missing or stale.

Safety Limits

Some actions are intentionally blocked until account or data safety checks pass:

• sensitive downloads can require account security checks;
• connection files must stay private and should be rotated if exposed;
• public support should not include tokens, passwords, API keys, client secrets, customer data, or connection files;
• broad permissions should be split before adding more access.

Caution

If a secret or connection file was shared publicly, rotate it before continuing setup or support.

When a Limit Looks Wrong

If Billing or the owner page shows a limit that does not match what you expect, include this in your support request:

• page or feature;
• plan name;
• current usage and limit;
• visible status or message;
• expected result;
• actual result;
• what changed recently.

Prepare a support request

Limits Are Clear When

You are done checking limits when:

• Billing confirms whether the plan allows the action;
• current usage is below or at the shown limit;
• the owner page explains the next step;
• any remaining issue has a support request with plan, usage, and visible status.