Tilt Base lets your members' AI transcribe recordings with your organisation's own transcription account, so usage is billed to you and your contract with the provider applies. Recordings go straight from your AI to the provider. Tilt Base never receives a recording or a transcript: it only gives your AI a short-lived credential for each one. An administrator sets this up once, in Tilt Base at **Settings › Organisation › Transcription**. ## Choose a provider
Provider Models Where recordings are processed What you connect
Azure Speech Fast transcription, Azure LLM Speech, MAI-Transcribe-2 Your Speech resource's region, such as Australia East A Speech resource in your Azure subscription. No key is stored.
Deepgram Nova-3 Australia (Sydney), the European Union or India, as you choose An API key from a Deepgram project
ElevenLabs Scribe v2 The United States An ElevenLabs API key
You can connect more than one account, including from different providers. Select **Add connection**, choose the provider and follow the steps below. Tilt Base checks every connection with the provider before saving it. ## Azure Speech Tilt Base reaches your Speech resource with access your Microsoft Entra directory grants, so there is no key to create, store or rotate. Usage is billed to your Azure subscription. ### Step 1: Grant access 1. Select **Grant access in Microsoft Entra**. An administrator of your directory signs in: a Global Administrator, Cloud Application Administrator or Application Administrator. 2. Check that Microsoft shows **Tilt Base**, from the verified publisher **TILT Legal Pty Ltd**, with application ID `d0d9b19c-3d21-433a-a60c-e4a529c12b31`. Then select **Accept**. 3. Microsoft brings you back to Tilt Base with your directory ID filled in. If someone else grants access, send them the link from the dialog and enter your directory ID yourself. It is the **Tenant ID** on the overview page of the Microsoft Entra admin centre. **Granting access does not open your Azure resources to Tilt Base.** It adds Tilt Base to your directory so that you can give it a role on a Speech resource. Tilt Base can reach only the resources you give it a role on, and uses them only to transcribe. ### Step 2: Create or choose a Speech resource **To create a new resource (recommended)** 1. Select **Deploy to Azure**. The Azure portal opens in a new tab with Tilt Base's template. 2. Choose a subscription, a resource group and the region recordings should be processed in. Australia East is the default. For Azure LLM Speech or MAI-Transcribe-2, choose Southeast Asia (Singapore), the closest region to Australia that offers them. 3. Select **Review + create**, then **Create**. You need the Owner or User Access Administrator role on the resource group, because the deployment gives Tilt Base a role. 4. Leave the Tilt Base dialog open. It connects the new resource by itself as soon as Azure has created it, usually within a few minutes. The template creates one Speech resource named `tilt-base-` followed by ten letters and digits, on Azure's Standard (S0) pricing. Key access is turned off, so only identities you grant can use it, and Tilt Base gets the **Cognitive Services Speech User** role on that resource alone. **To use an existing resource** 1. In the dialog, select **Use an existing resource instead**. 2. In the Azure portal, open the resource's **Access control (IAM)** page and select **Add › Add role assignment**. Choose **Cognitive Services Speech User**, then under **Members** select **Tilt Base**, and select **Review + assign**. 3. If the resource has no custom domain name, generate one on its **Networking** page. Leave public network access on, because your members' AI sends recordings from its own environment. 4. Back in Tilt Base, the resource appears in the dialog within a few minutes of getting the role. Select **Connect** beside it. Once one resource is connected, Tilt Base skips the grant step for the next. **Where recordings are processed.** Azure processes each recording in its Speech resource's region. Azure LLM Speech and MAI-Transcribe-2 run only in Central India, East US, North Europe, Southeast Asia, West US and West US 2. To keep fast transcription in Australia and use those models too, connect one resource in Australia East and one in Southeast Asia. ## Deepgram 1. In the Deepgram console, create a project used only for Tilt Base, so its usage and billing are separate. 2. In that project, create an API key with the **Member** role. Member is the lowest role that can issue the temporary tokens Tilt Base gives your AI; do not use an Owner or Admin key. 3. Set an expiry if your policy requires one, and connect a new key before it expires. 4. Paste the key and select **Connect**. Tilt Base stores it encrypted and shows only its last four characters. When you add Nova-3, choose where it processes recordings: Australia, the European Union or India. ## ElevenLabs 1. In ElevenLabs, open **Developers › API Keys** and create a key for Tilt Base. Any plan works. 2. Turn on **Restrict Key** and give it access to **Speech to Text** only. Set a credit limit if you want to cap usage, and keep **Auto-disable if leaked** on. Leave IP restriction off, because Tilt Base's addresses change. 3. Paste the key and select **Connect**. For each recording, Tilt Base gives your AI a single-use token that expires after 15 minutes. The key itself never leaves Tilt Base. ## Add models After your first connection, Tilt Base asks which model to add. Add each model your members should use and choose a default. Your members' AI uses the default unless someone asks for a particular model, and each model shows where it processes recordings. ## Changing or removing a connection - **Replace a key or resource without downtime:** connect the new one, move your models to it in each model's settings, then disconnect the old one. - **Disconnect** is in the connection's **…** menu. Models that ran on it stay added, marked **Needs attention**, until they run on another connection. - After disconnecting, revoke the key with the provider, or in Azure remove Tilt Base's role from the resource, if you no longer need it. ## Troubleshooting - **Tilt Base was not found in that directory.** Access has not been granted yet, or the directory ID is wrong. Grant access, then wait a minute; Microsoft can take a moment to register it. - **The deployment fails with an authorisation error.** You need the Owner or User Access Administrator role on the resource group. - **The new resource has not connected.** Keep the dialog open and select **Check now**. Azure can take a few minutes to apply a new role. - **An existing resource is not listed.** Check that Tilt Base has the Cognitive Services Speech User role on that resource; a new role can take a few minutes to show. A custom role must also allow reading the resource. - **A resource is listed but cannot be connected.** Tilt Base says why: generate a custom domain name on its Networking page, or use a region with Azure fast transcription. - **Anything else.** Contact [support@tilt.legal](mailto:support@tilt.legal).