Settings and Billing

The Settings section in Console is used to manage the account, token, and limits.

Account profile

Here you usually have access to:

• email;
• contact name;
• company;
• the internal account identifier;
• saving the profile.

Keeping the profile up to date is useful not only for support, but also for Console login itself: the token is linked to the email from the account profile.

Token rotation

In Console, you can request a new token. In practice, this looks like this:

• the current token is revoked;
• the new token is sent by email;
• after that, you need to log in to Console again;
• then update the token in all external applications and secrets.

This is a convenient and safe way to replace a token either on schedule or after suspected compromise.

Logout and session end

The logout command ends the current web session in Console. The token itself is not necessarily revoked — this is a logout from the interface, not a full secret rotation.

Billing, limits, and usage

In Overview and Settings, Console usually shows:

• the current plan;
• resource limits;
• an estimate of current consumption;
• how close you are to the limits.

These numbers are needed for operational control: to understand in advance whether the current plan is sufficient and to avoid unexpectedly hitting limits while creating new resources.

Important: the displayed consumption value is an operational estimate for management, not necessarily a final accounting invoice.

Account deletion

Account deletion is an extreme and destructive operation. Before using it, it is recommended to check:

• whether any required databases remain;
• whether applications still use resources;
• whether backups or migrations have been completed;
• whether all team members have been informed.

In the user scenario, deletion requires confirmation with the current token and removes associated resources.

Practical recommendations

• use separate tokens for people and for CI;
• grant the minimum permissions required;
• track limits in advance, not only at the moment of refusal;
• always check dependencies before deleting an account or tenant.

This makes SPG99 operations safer and more predictable.