Skip to main content

Account

The Account section contains account information and settings. This is where users can add settings required to connect to Azure CLU, to use an Azure resource for Teneo copilot features or create Secrets.

note

Only users with sufficient User permissions can add or edit any of the settings.

Account Information​

The Account Information section provides information related to the Teneo account's name and Id.

The Settings defined under Account can be used by any solutions in the account.

The Account tab is found in the main solution window in Studio Desktop.

account example

Settings​

Secret Specifics​

A Secret setting requires a name and a value. A description can optionally be added. The value becomes a secret as soon as the secret is saved. Secrets can be accessed from any solution in the Account via the global Secret script. For more information, visit the page on Secrets.

info

Secrets are a way of allowing users of Teneo to store, manage, and use any secret/sensitive information, such as API keys, tokens, passwords, etc., in a secure and controlled way in the Platform.

Azure OpenAI Specifics​

An Azure OpenAI Setting is used for enabling the Teneo Copilot feature, which uses an LLM through Azure. This setting will not be used for other Gen AI tasks in the solution.

An Azure OpenAI setting requires the following information:

  • Name
  • (Optional) description
  • Resource Name/Group (found in Azure AI Services)
  • Deployment Id (found in the Azure AI Foundry, under Deployments)
  • API Key (found in Azure AI Services)
  • Model (a read-only value that appears after first Save action is performed)

It is possible to add more than one LLM - Azure OpenAI Setting to an account and a new Setting is added as deactivated per default. The developer can choose which setting (if any) should be active, leaving the others deactivated. The activated setting is the one used in for Teneo Copilot features for any solution in the account.

In Azure AI Services, you can find the resource group, API keys, and other information related to the resource:

azure specifics

In Azure AI Foundry, you can find the Deployment name or Id, the model that is used, and other information related to the deployments.

azure ai foundry

CLU Specifics​

For a CLU Setting, add the Language service Resource name and API key. You can have one CLU setting per Account, so the option to add a CLU setting is only available when no CLU setting has been configured.

In Azure AI Services | Language services, you can find the information required to connect to a CLU model.

CLU specifics

For more information, visit the page on CLU Manager.

API Key Management​

Be aware of the following related to the management of API keys:

  • Keys are uploaded to Teneo where they are stored (encrypted).
  • The users of Studio bring their own key and upload the key themselves.
  • A specific Studio permission is needed to modify Settings; see User permissions.
  • It is not possible to read the keys (encrypted) via the API nor the UI (Studio).
  • It is possible to overwrite/update the key if the user has the correct/needed permission.