Organizations & networks

About organizations & networks

In Kevel, your organization is the overarching entity for your company.

An organization includes one or more networks that represent development and production spaces, and/or separate brands that your company manages. Ad, reporting, and inventory data for each network is entirely self-contained.

📘

Example: Gardener's Weekly's networks

The company Gardener's Weekly has a single organization, called gardenersweekly. It also has the following networks:

• gardenersweekly-dev
• gardenersweekly-prod

Each employee within gardenersweekly has access to gardenersweekly-dev, or gardenersweekly-prod, or both.

Authorizing default network access for SSO integrations

Kevel can configure the network(s) that your users will automatically gain access to when granted authentication rights via your IdP.

To configure default network(s) for IdP user access, contact Kevel support.

📘

Example: All new users get production network by default

Gardener's Weekly could specify that all users added to the Kevel group in their Okta instance should automatically gain access to gardenersweekly-prod.

--> As a result, a user newly added to the Kevel group in Gardener's Weekly's Okta could log in to the gardenersweekly-prod network immediately.

They can do so without additional action by a Gardener's Weekly administrator.

📘

Example: Manually add all users to networks

Alternatively, Gardener's Weekly could decide that there is no default network for new users.

--> As a result, a user newly added to the Kevel group in Gardener's Weekly's Okta could log in to Kevel, but would not be able to access any network data. They would see a "You don't have access to any networks" error message in the Kevel UI.

In order to allow the new user to access any network(s), a Gardener's Weekly administrator would need to specify those permissions within the Kevel UI.