Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Connect Slack membership and billable indicators. Read workspace role flags and periodic billing eligibility without reading conversations. Current availability: Read adapter implemented; company authorization and successful live sync required.

Before you start. An authorized company administrator with Vendor licenses management permission and an approved provider data-use scope. The company’s protected integration vault. Use a dedicated provider application; never put credentials in a KB, video, chat or source file.

Step 1. Use an approved workspace user token with admin, users:read and users:read.email. The admin scope also permits other Slack operations; restrict the application and its operators accordingly.

Step 2. Enter the expected workspace ID beginning T and the protected xoxp user token. The token must identify that exact workspace; an organization-wide token is not accepted by this setup.

Step 3. Save the encrypted connection in Companies > company > Vendor licenses. Choose Sync now in production after provider authorization. Dev and QA isolate external operations. Review the recorded sync result and compare the snapshot with the provider console.

Step 4. Review billable and non-billable member cohorts separately. Slack computes billing eligibility periodically, so it may lag recent activity. It is not a purchased-seat count.

Step 5. Inspect returned owner, administrator and guest flags. The reader does not request conversation messages, channel history or a full effective-permissions assessment.

Now verify the result. Test a deactivated or non-billable member and compare with Slack’s current billing view. It must not be labeled as an active billable seat. A successful company sync is required before describing the connection as healthy; an available adapter alone is not a connected account. Check a second company and a view-only account: neither can change this company’s credentials or lifecycle state. Pause, Resume and Trash affect only the local connection. Resume waits for a separate Sync action; no vendor user or license is modified.

If you get stuck. 401 or 403: check credential expiry, the selected provider organization and the exact required permissions. Do not grant broad write access merely to bypass a failed read. A failed or incomplete provider response preserves the last complete snapshot. Review the error, correct the connection and explicitly retry. On a 429 rate-limit response, wait for the provider’s retry window before another manual sync. Large inventories can require a separately designed scheduled export; the current bounded sync does not commit partial results.

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.