Skip to main content

Setting Up the Environment

Every organization receives its own environment within AI-Public. This environment must be selected before login options are displayed.

Environment Configuration​

Environment setup is typically done at the organizational level. Multiple branches can be included under this level. However, a large organization may want to make further subdivisions between different divisions or departments. In such cases, multiple environments can be set up for the organization.

Each environment receives its own database and account silo within Google Cloud. We utilize the multi-tenant feature of Google Identity Platform and the multi-database feature of Google Cloud / Firebase.

After registration, AI-Public will take the following steps:

  • Creating a new tenant on Google Identity Platform
  • Linking the desired login methods to this tenant
  • Optionally linking a Microsoft Entra Application to the tenant
  • Creating a new database within Google Cloud
  • Filling in the organization's details
  • Setting up API Keys for various integrations

Basic organization details will be filled in.

API keys will be set up for:

  • OpenAI: GPT models and GPT Image models
  • Google Cloud Vertex AI: Gemini models, Nano Banana and Gemini TTS
  • Mistral AI: Mistral and Voxtral models
  • Anthropic: Claude models
  • Black Forest Labs: FLUX image models

Usage costs will also be charged to these API keys. For large accounts, we offer the possibility to provide your own API keys. When supplying your own API keys, we can offer significant discounts.

Setting Up User Migration​

When creating or editing an environment, you can configure whether users may migrate their own data from an earlier environment. This setting is Off by default.

The available options are:

  • Off: users do not see a migration option in their account.
  • Demo: users can transfer data from the demo environment.
  • Plein: users can transfer data from Plein.

When migration is enabled, the user sees the Migration tab in Profile. AI-Public checks there whether an account exists for the same user in the configured source environment. Only when data is found can the user start a migration.

When starting the migration, the user chooses which parts should be transferred. Migration is intended for personal data, chats, chat messages and files. Staff data and user roles from the source environment are not migrated.

After a migration has been completed, the same user cannot start the migration from that source environment again. The migration runs in the background, so the user does not have to keep the page open.

AI-Public Sets Up the Environment​

Initially, AI-Public will set up your environment at a basic level after mutual consultation. At least 1 Environment Admin account will be transferred. This Environment Admin can modify all environment settings.

This Environment Admin will then be responsible for further environment setup, such as creating additional admin accounts for branches.

Setting Permissions​

Setting permissions is also part of the basic data settings. Permission setting is addressed under the Privacy section. We refer to the relevant article.

Setting Domains​

Setting domains is also part of the basic data settings. With domains, you can whitelist domains so you don't need to enter accounts via CSV lists or manually. Users with the correct domain will be directly linked to a branch and receive the Employee role or a general user role based on the domain name. We refer to the relevant article.

WhatsApp