Tenants in Console

A tenant in SPG99 is an isolated administrative container for your databases and the access associated with them. The easiest way to think about it is as a separate workspace.

When it makes sense to create separate tenants

Most often, separate tenants are useful for:

• different projects;
• production, staging, and development;
• different teams;
• different customers.

This approach keeps the structure understandable even when the number of resources grows.

What you see in the tenants list

In the Tenants section, you usually see:

• the tenant name;
• the creation date;
• the number of databases inside;
• quick actions such as opening the tenant page and deleting the tenant.

If your API key has tenant scope, you will only see the tenant that key is bound to.

Creating a tenant

When creating a tenant, you specify its technical name.

Name recommendations:

• start with a Latin letter or _;
• then use Latin letters, digits, _, $;
• avoid spaces, Cyrillic, and overly long names.

Good examples:

• app_prod
• billing_stage
• team1

After creation, Console shows:

• pg_user;
• pg_password;
• dsn_template.

These values are very important to save immediately, because they are exactly what is needed to connect to any database inside the tenant.

What is on the tenant page

A tenant page usually contains:

• the name and creation date;
• the number of databases;
• the connection template;
• tenant access data;
• the list of databases inside the tenant.

This page is useful for:

• verifying that the tenant was created correctly;
• quickly navigating to the required database;
• assembling the final DSN;
• creating a new database.

Deleting a tenant

In the managed user scenario, a tenant cannot be deleted blindly. If it still contains databases, you must delete them first or use the cascade scenario through the API.

This is a protective mechanism: it prevents you from accidentally removing a container that still includes working resources.

The main thing to remember

A tenant is not just a pretty folder in the interface. It is the key unit of structure and access in SPG99. If you plan your tenant structure by projects and environments from the start, the rest of Console remains understandable and scales well together with the number of databases.