Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Connect and govern provider services. Configure a provider for one company, verify read access, enable paged synchronization and retain clear lifecycle evidence. 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. TLS owners open Command Center > Connected services. Company Workspace administrators use Integrations > Connected services. Managed IT clients can view licensed results; TLS manages their protected provider configuration.

Step 2. Choose the service and review its exact supported operation. A catalog listing or saved configuration does not mean the account is connected. Confirm the customer’s paid product, plan and selected services.

Step 3. Use Configure to enter credentials only in the protected form. The TLS platform and each company have separate secret records; saving one does not copy it to another company or Dev/QA. Record the real provider expiry or a planned rotation date.

Step 4. Select Verify read access. Confirm the provider tenant, mailbox, company or project is correct. Verification reads a bounded page without purchasing licenses or generating AI output. Configuration changes clear old verification.

Step 5. Enable synchronization after successful verification. Read the next page or let an accepted scheduler continue from the stored cursor. Current means the present pass completed; inspect its measurement time and run history.

Step 6. Use search, dates and page controls for recorded results. Recheck source permissions before opening a provider link. Last seen is a local observation time, not proof the provider account remains active indefinitely.

Step 7. Pause to stop collection. Delete moves a connection to its 60-day recycle period. Restore leaves it paused and requires new verification. Permanent removal deletes local credentials and cached results; it does not delete the vendor account. Retention holds apply.

Now verify the result. A company cannot select another company or the TLS platform scope. Changed credentials require new verification; expired credentials stop synchronization. A running connection cannot be deleted while it holds its execution lease.

If you get stuck. Actual consent, protected credentials, complete provider pagination and a scheduled invocation must be accepted. No provider account was authorized merely by publishing this guide. Dev and QA block external actions by default. They do not use production service credentials.

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.