At Okta, we see our customers deploy and build a broad range of customer-facing apps. Commonly, these apps support differing audiences, often reflected as segments within a single company, identities across customer companies, or users that span into partner organizations. Which begs the question: how to centrally manage these diverse users while ensuring the proper level of security and data privacy? When working with such different entities, one must consider several variables, such as customer data access, data separation, and user experience. Each of these variables can be the driving force behind a multiple Okta tenant structure. Why multiple Okta tenants? If your organization is faced with a diverse set of user types, consider the Okta tenant segregation model. This model separates each Okta tenant with its own data, network performance, and feature set, making each tenant its own entity. It also serves to add an additional.