Okta Organizations
Explore the structure of Okta organizations, including user and application management, organization-specific URLs, and feature categories. Understand production versus preview environments, how to use the Admin Console, rate limits, and options for single versus multiple organizations to effectively manage authentication solutions.
An Okta organization is a root object that contains all other Okta objects.
Every Okta organization has users and applications that must be configured to use Okta. Users can be entered into the Okta ecosystem using the following methods:
- Users are directly made in Okta.
- Users are imported into Okta through Okta’s directory integrations.
- Users are imported through application integrations.
Applications in an Okta organization can be public ones such as Slack or Zoom, or in-house, custom-built applications.
Organization features
Based on different contracts, Okta organizations can have different features. Let’s take a look at some categories of features below:
-
Generally Available (GA): GA features are relatively newer and are supported by Okta customer support and any problems are handled as specified by the Customer Agreement with Okta.
-
Early Access (EA): This is an optional feature that can be enabled in an organization by contacting Okta Support. Super Admins can also enable or disable some EA features from the Features page in the Okta Admin Console, given that their organization is eligible for them. ...