New tenant creation

This article lists the steps that are taken to provision a new tenant, including the decision points affecting setup.

Steps

Choose authentication provider

Flowgear offers authentication either via a Microsoft or Google ID (using OpenID Connect).

• Configure platform authentication via Microsoft ID
• Configure platform authentication via Google ID

Choose version control provider

You can opt in to using a version control system as the backing store for Workflow definitions. When selected, the Revision Management system commits the Workflow to a specific version control branch when it is saved.

Under Release Management, customers can promote workflows from one Environment to another via the Console or directly use Pull Requests within Version Control.

See Setting up a Version Control Token for more information on how to configure a version control token in Github.

If you don't want to use Github, we also provide a default storage option. Under this configuration, the experience within the Console is virtually identical but the source JSON for the workflows is stored internally to Flowgear and not within Github.

Choose API-binding hostname

For plans that include Enterprise API, customers can specify their desired hostname for the API endpoint. For example yourcompany.flowgear.net.

On certain plans, you'll be able to completely white-label the hostname - for example api.yourcompany.com. In these cases, we'll ask you to provide us with a TLS certificate that includes the subject CN=api.yourcompany.com and will provide you with information to create the appropriate DNS records.