Organization

Because a company will typically have more than one Analytics Environment, these Environments are contained within an Orbit One Organization. Accesses are based on Organization “membership”, meaning people within a company with access to Orbit One, have access to the Environments in their Orbit One Organization (depending on their role).

An Orbit One deployment is single-tenant and thus represents a single Organization. The reason behind this design is mostly related to simplifying security and reducing risk of cross-organization contamination. One consequence is that most of the general settings that pertain to Orbit One as an application, are referred to as Organization Settings.

Platforms

Orbit One brings together different Analytics Platforms within an Organization, including:

• Tableau (currently supported)

• Power BI (partially supported)

• Thoughtspot (future)

• Looker (future)

• Etc.

Modules

See: Modules.

Environments

One Environment represents an Environment within a Platform. This has a different meaning depending on which Platform we’re dealing with. Adding an Environment to Orbit One is done by an Orbit One Admininistrator.

Tableau Environment: Site

When the platform is Tableau, an environment is represented by a Tableau Site. Adding an environment entails just providing a REST API PAT, and the URL to the site. When one Tableau Server or Cloud deployment spans multiple sites, these can be added to Orbit One as separate Environments.

Power BI Environment: One or more Workspaces

To connect Orbit One to Power BI, we set up a Microsoft Entra App, which is granted access to one or more Power BI Workspaces. While a Workspace bears resemblances towards a Tableau Site, the fact that we can grant a single App (i.e. a single Orbit One connection) access to more than one means that it’s not equal to an Environment. Instead, the Workspaces to which the Entra App has access jointly represent the Orbit One Environment.

For more information on how to integrate Power BI with Orbit One: Microsoft & Power BI.

An Environment as the Context

Different components of Orbit One, as well as its modules, will operate within a context defined by a specific Environment.

• When using most Modules, the content reflected is the content in the context of a single Environment. For example, setting up Insight Messaging happens within the context of a single environment on the configuration page.

• Some Modules extend across Environments. For the Portal Module, all Environments are used at once. The Browse Module has certain views that combine content from multiple Environments, too.

• The concept of Platform is less relevant when referring to this concept of context, as the Environment of the Context directly defines its Platform.