Skip to main content

​
Keys

Open Keys from the Hub navigation. The page separates credentials by ownership.

​
Personal tab

The Personal tab contains two sections.

​
Provider keys

Add a provider key by selecting a provider and entering the credential. You can also:
  • Add an optional nickname
  • Mark the key as primary
  • Mark the key as fallback
  • Show or hide the value while entering it
  • Edit or delete an existing key
  • Review the status or reported error shown by the Hub
The provider list shown in the dialog includes model, voice, infrastructure, and integration providers and may change over time.

​
Personal B-Bot API keys

Personal B-Bot API keys are separate from provider credentials. When creating one, you can add a label and mark it as primary.
Copy a newly created B-Bot API key when the Hub displays it. Store it in an appropriate secret manager. Do not paste it into chat, commit it to source control, include it in documentation, or expose it in client-side code.
Existing entries show their label, status, primary marker, and final characters. You can delete keys you no longer need.

​
Company tab

The Company tab is available only when you belong to at least one company. It manages provider keys for the active company. Company scope has these limitations in the current Hub:
  • It is tied to the active company.
  • It contains provider keys only.
  • Personal B-Bot API keys are not created in company scope.
  • Available actions can depend on your company role and account permissions.
You can also reach the same company provider-key panel from the Keys tab on the Company page.

​
Minimum safe handling

Treat every key as a secret:
  1. Use only the permissions required for the intended integration.
  2. Keep personal and company credentials in the correct scope.
  3. Remove keys that are no longer needed.
  4. If a key may have been exposed, revoke or rotate it at the provider and replace it in the Hub.
  5. Review provider-side usage and access controls as appropriate for your organization.
The Hub UI does not establish a security or availability guarantee for a provider credential. Refer to the relevant provider’s current documentation for account-specific creation, restriction, rotation, and incident procedures.