Quotas and Limits
Quotas and limits define the maximum number of resources that can be created or accessed within the SmartThings platform. Enterprise accounts have higher limits in several areas to support larger-scale deployments.
For information about API rate limits (request throughput), see Rate Limits and Guardrails.
Many of these limits can be adjusted to meet your specific deployment needs. If your use case requires higher limits, contact your SmartThings account manager to discuss available options.
Exceeding a Quota
A request that would exceed a quota fails with a 422 validation error. The error response includes the name of the quota that was reached, such as accounts-per-user or locations-per-account.
Per User
A user can access up to 10 accounts at the same time. Any access within an account counts toward this limit, whether that's a single location or an IoT Manager role across location groups.
This limit matters most to system integrators, who often keep each customer's deployment in a separate account. A technician who works across more than 10 customers will reach it. After that, granting them access to an 11th account fails, for example when assigning them an IoT Manager role in another customer's account.
| Resource | Limit | Notes |
|---|---|---|
| Accessible accounts | 10 | Any access within an account counts |
| Locations with consumer app access | 10 | Above this, the user can't use the SmartThings mobile app or my.smartthings.com |
To free up an account slot, remove all of the user's access to an account they no longer need. You can do this through the API or the SmartThings Pro Dashboard. Removing only some of their access isn't enough: the account keeps counting until the user has no access left in it.
The consumer app limit doesn't block access. A user can still be given access to more than 10 locations, such as an installer who doesn't need consumer apps, but they lose access to those apps. This is separate from the accessible accounts limit.
Per Account
| Resource | Limit | Notes |
|---|---|---|
| Locations | 300 | |
| Location groups | 300 | |
| Installed apps | 500 | |
| Installed API-only apps | 20 | |
| Users with access | 1,500 | |
| Service accounts | 20 |
Enterprise Eventing
For guidance on structuring your sinks, subscriptions, and filters within these quotas, see the Subscription Design Guide.
| Resource | Limit | Notes |
|---|---|---|
| Sinks per account | 10 | Webhook endpoints that receive events |
| Subscriptions per account | 10 | Filter configurations attached to sinks |
| Filters per subscription | 10 | Filter groups within a subscription (OR logic) |
| Event types per event type filter | 10 | |
| Capabilities per capability filter | 10 |
Per Location Group
| Resource | Limit | Notes |
|---|---|---|
| Locations | 300 |
Every location belongs to a location group. Locations per account, location groups per account, and locations per location group are separate limits, and any one of them can be reached on its own. For example, 300 groups of 300 locations each would allow 90,000 locations, but the account still stops at 300 locations in total.
Per Location
| Resource | Limit | Notes |
|---|---|---|
| Devices | 300 | |
| Rooms | 20 | |
| Modes | 25 | |
| Rules and Scenes | 1,000 | Shared limit between rules and scenes |
| Accepted location share invitations | 20 | |
| Users with access | 20 |
Per Device
| Resource | Limit | Notes |
|---|---|---|
| Devices per device group | 50 |