diff --git a/app/learn/concepts/multi-tenant-data/page.md b/app/learn/concepts/multi-tenant-data/page.md index 490c4925b..597c2827e 100644 --- a/app/learn/concepts/multi-tenant-data/page.md +++ b/app/learn/concepts/multi-tenant-data/page.md @@ -133,7 +133,7 @@ As part of choosing a data partitioning model, you must also consider how a give | **_Security\*_** | Hierarchically deterministic derived encryption passphrase per tenant | Bucket name not encrypted; Hierarchically deterministic derived encryption passphrase per tenant | Project Name not encrypted | | **_Billing_** | Aggregated usage and billing | Metered Usage per BucketAggregated Billing | Metered Usage per Bucket Invoice per Project | | **_Default Limits_** | 100m max objects per Bucket (based on Project limit) | 100 Buckets per Project | 3 Projects per account | -| **_Hard Limits_** | None | 10,000 | 1,000 | +| **_Hard Limits_** | None | 1000 | 80 | | **_Other Considerations / Restrictions_** | Lexicographical listing of Tenants not supported with default encryption | S3 Bucket naming restrictions applyPlacement rules available | [Management API](https://github.com/storj/storj/blob/main/satellite/console/consoleweb/consoleapi/gen/README.md) availablePlacement rules available | ## Isolating and Ensuring Tenant Object Privacy with Encryption Keys