# Can a contractor use one Slack channel instead of a paid seat?

> Keep paid Slack while testing a contractor's single-channel guest role, remaining DMs, historical files, guest capacity and the actual billing adjustment.

Updated 2026-10-21 · https://onelesstool.com/guides/slack-contractor-seat-reduction

**A genuine external contractor may no longer need a paid Slack seat when their recurring work fits one channel, the remaining workspace supports the guest count and billing confirms the adjustment.** Keep paid Slack for the team. This is a role test inside the existing workspace, with its current projects and history.

Slack offers guests on paid plans. Multi-Channel Guests are billed like regular members; Single-Channel Guests have no separate charge within an allowance of five per paid active member. [Slack guest roles and billing](https://slack.com/help/articles/202518103-Understand-guest-roles-in-Slack).

The useful question is whether one channel contains the work the contractor must actually do. A smaller role is a poor fit if it turns a colleague into a permanent relay for missing conversations.

## Choose one complete contractor job

Start with a current statement of work and recent completed assignments. List the channels, people, files and app actions involved in receiving a request, resolving a question and delivering the result. Include exception work: a rejected deliverable, a correction to last month's decision or an urgent request while the usual contact is away.

For example, an outside copy editor might receive briefs, ask questions and deliver revisions in one project channel. That is a candidate to test, not proof of eligibility or savings. If the editor must also follow separate product and release discussions, put those dependencies in the inventory rather than pretending they are occasional noise.

Name a primary contact and backup who already have appropriate access. Agree where authoritative instructions and approved deliverables belong. If necessary material is scattered across other channels, decide whether the work can sensibly be organized in one place without exposing unrelated conversations. Include that maintenance effort in the decision.

Retain Multi-Channel Guest access or membership when the contractor needs several channels, broader responsibilities or unsupported actions. Rotating a guest between channels throughout the day would defeat the proposed operating model.

## Recalculate guest capacity after the reduction

Use the proposed number of **paid active members**, not the old invoice's headcount, to check the allowance. Record all existing Single-Channel Guests, the contractor being converted, planned arrivals and any members leaving at the same renewal. Compare the resulting guest total with five times the remaining paid active member count. [Guest capacity rule](https://slack.com/help/articles/202518103-Understand-guest-roles-in-Slack).

If that comparison fails, stop the proposal and obtain an account-specific resolution. Do not assume Slack will preserve an over-limit arrangement or that one quiet month establishes permanent capacity. Set a named administrator to review this count whenever the paid team changes.

Workspace owners and admins manage guest roles. Slack documents conversion from a regular member through the account-type controls; Enterprise users belonging to several workspaces follow a different organization-level process. Confirm the applicable route before scheduling the change. [Changing Slack roles](https://slack.com/help/articles/218124397-Change-a-members-role).

## Check DMs, files and apps separately

One channel does not mean one communication path. Guests can initiate DMs with members sharing their channel; members can initiate DMs with guests, subject to Grid workspace membership. Existing DMs survive channel or role changes. Guests can see message and file history in their accessible channels. [Guest permissions and DM caveat](https://slack.com/help/articles/202518103-Understand-guest-roles-in-Slack).

Inventory necessary DMs and review whether older conversations remain appropriate for this contractor. Do not describe the role change as revoking all earlier contact or creating complete isolation. If the actual goal is ending access to sensitive conversations, the administrator needs to address that separate requirement before using this proposal.

Slack's role table permits guests to send messages and upload files, but excludes app installation and workflow building. [Permissions by role](https://slack.com/help/articles/201314026-Permissions-by-role-in-Slack). Guests also cannot authorize their Slack account for apps; workflow use depends on the workflow's permissions. [Guest app and workflow boundaries](https://slack.com/help/articles/202518103-Understand-guest-roles-in-Slack).

Identify the exact actions required: opening a linked Drive document, invoking an approval workflow, receiving an app notification or adding an attachment. A bot appearing in the channel does not establish that the guest can complete the job. Have an authorized internal operator own app administration, and test external file permissions through the contractor's own identity.

## Run the unexecuted contractor pilot

The following pilot is **unexecuted**. Use one ordinary assignment and one historical correction, with the administrator available. Record the current role, channel memberships, required DMs, billing terms and restoration contact. Leave Slack's plan and project records in place.

1. **Capture a baseline.** The contractor completes the task once under current access. Record inputs, output location and any intervention by a colleague.
2. **Apply the proposed role.** After checking capacity, the administrator changes the contractor to Single-Channel Guest and confirms the assigned channel. The contractor signs in normally and verifies the role's practical access.
3. **Complete live work.** Receive a brief, ask a question, upload the agreed output and complete each required app action. Require the intended recipient to find and use the result. Log blocked steps and time spent relaying information.
4. **Retrieve older work.** Give the contractor a real question about an earlier decision and its supporting file. Require the correct answer through their normal Slack access. Have an ordinary internal reader, without admin tools or the author's coaching, repeat the lookup.
5. **Exercise backup coverage.** With the primary contact unavailable, the backup handles a clarification and validates the delivery. Use a harmless restricted test channel to check that channel boundaries match the agreed inventory; review surviving DMs separately.

Set an acceptable retrieval time and support burden before the trial. Fail it when necessary history is unreachable, a file requires someone else's session, an app action fails or repeated relay work replaces direct participation. Restore the suitable role and intended channel memberships with the administrator, then repeat the failed task. Record any billing consequence of restoration.

Keep paying when broad channel context or direct app work is essential. Keep the current arrangement if the backup cannot operate it or capacity is uncertain. A successful demonstration by the workspace owner is not a pass for the contractor.

## Separate credits from money saved

Slack's fair-billing policy covers subscriptions and add-ons bought through its website using a credit card or self-serve invoicing. It describes adjustments for active-member changes and credits toward future payments; credits are nonrefundable, nontransferable and expire when the paid subscription ends. Do not generalize those terms to a negotiated contract. [Slack fair billing](https://slack.com/intl/en-gb/help/articles/218915077-Slacks-fair-billing-policy).

Give the billing owner the actual role-change date, current invoice, proposed member and guest counts, add-ons and remaining commitment. Ask what this specific conversion does to the next statement and renewal. Record any credit separately from cash returned; the guide does not establish a refund or a particular conversion-credit date.

Compare **current Slack charge minus confirmed remaining Slack charge minus incremental costs** over the same term and currency. Count retained Slack once. If a credit is already included in the revised statement, do not deduct it again as another saving. Keep one-time setup and recurring coordination effort separate, and reconcile the next invoice with the approved proposal.

Use the [subscription audit](/audit) to record the smaller retained arrangement only when the tasks and billing both support it. For ongoing reviews, see [Stack Watch](/pricing) for current options and availability.