How do I handle multi-tenant document storage?
Represent each tenant with a FormKiQ site when tenants can share one AWS deployment. Site permissions separate their document spaces, while infrastructure and service limits remain shared. Use separate deployments for tenants requiring independent accounts, regions, encryption configuration, or operating boundaries. Always authorize the tenant mapping instead of trusting a supplied site ID.
Pick the isolation model
A site is a logical document partition, not an AWS account or separate region. One deployment can host sites for departments or SaaS customers. Separate instances provide a stronger operational boundary and permit different deployment settings, upgrade schedules, and regional placement.
Core's Automatic Sites model derives access from identity-provider groups. Commercial Defined Sites allow explicit site creation and group-to-site permission assignment. Changing between the models requires access planning; existing group names alone do not restore Defined Sites permissions.
Make requests tenant-aware
Resolve the intended tenant from the authenticated identity and authorized business context, then include siteId consistently. Store the site alongside each document ID in application records and integration messages. Avoid making user email addresses permanent tenant identifiers unless your identity lifecycle handles renames and deletion.
Verify isolation through API requests for lists, search, document IDs, downloads, and processing outputs. Monitor noisy-neighbor effects, per-tenant volume, and reconciliation jobs. A shared application's service credential needs its own tenant checks even when the underlying deployment is multi-site.
Edition and configuration
Core supports Automatic Sites; Defined Sites are commercial. Advanced and Enterprise offer flexible multi-instance/multi-region licensing. AWS account and regional isolation require separate deployment architecture.