Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Anthropic Claude setup and acceptance. Create reviewed drafts with an authorized Claude API account. Provider usage is separate from the workspace license. Current availability: Implemented; verification required.

Before you start. An authorized administrator in the correct company or the TLS owner console, with mandatory verification completed. Use an approved synthetic account for acceptance. Keep credentials, personal data and recovery codes out of recordings.

Step 1. Create a dedicated provider API project or account, restrict its key, set an appropriate provider spending limit and choose a model already enabled for that account.

Step 2. Open Connected services > Anthropic Claude. In the correct company or TLS scope, enter Anthropic API key, Enabled model ID in the protected form. Record the provider expiry or planned rotation date.

Step 3. Save and Verify read access. Confirm the returned identity and records with the vendor console. A failed verification stays a setup issue; it cannot be treated as a working connection.

Step 4. Enable synchronization. Review the complete paged pass and its timestamp. Search saved records and open source links only when your provider account permits it.

Step 5. For a draft, type only the approved prompt, confirm the provider-usage acknowledgment and request one draft. No customer records are attached automatically. The response is for human review and is never published or sent automatically.

Step 6. This release limits input to 12,000 characters, requests up to 2,000 output tokens and permits 20 draft attempts per provider per day. A timed-out request may still incur provider usage; it is not automatically retried.

Step 7. Pause before offboarding or credential replacement. Saving new credentials clears verification. Recycled connections retain a 60-day recovery window, with restoration paused until reverified.

Now verify the result. Minimum catalog eligibility: Professional. Selected service dependencies and an active paid subscription also apply. TLS platform credentials and company credentials remain separate. Accept one complete provider pass and a real scheduled continuation before claiming the service is connected.

If you get stuck. Provider API usage and subscriptions are separate. A workspace license does not include unspecified model usage.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.