Understand company billing and seats

Who counts as a seat

A seat is a unique active human in at least one active company team, counted once across teams and connected workspaces. Slack-only people and guests count; bots, pending invitations, suspended people, archived teams and people without active teams do not. Suspending a member reduces active access, not historical records. The company owner is protected from suspension in Billing.

Proposed monthly pricing

The published USD figures are proposed, before-tax rates and have not been approved as live prices. A paid purchase is available only when the company billing configuration explicitly enables it. Core task features are not described as separate paid tiers.

• The first 5 active people are $0 per month; no card is required for the free allowance.
• People 6 through 25 cost $4 per person per month.
• People 26 through 250 cost $3 per person per month. The price is graduated: the first five stay free and the later bracket applies only to seats in that bracket.
• Capacity from 251 people requires an explicitly approved enterprise contract, including its quantity, price, and payment terms. It is not an automatic plan change.

Manage people and team assignment

1. 01An organization owner or billing administrator opens Company → Billing.
2. 02In Company seats, suspend an eligible member to reduce active access, or restore a suspended member when needed. Suspension is separate from deleting the company or its data.
3. 03To assign existing company people to another team, choose the team and members, then select Add selected users. You can also use Add Member on a team page.
4. 04The user count is calculated automatically. Your first 5 users are free. Adding a sixth user prompts for payment details; later paid additions show the prorated charge and new monthly total before you confirm.

Capacity changes and payment

There is no need to choose or buy capacity separately. When you add users, Slackalendar calculates the required count and shows the before-tax monthly total and charge due today. After the first paid billing setup, additional users are prorated for the remainder of the billing cycle. Confirm once to proceed; users are added automatically after payment is confirmed. If payment needs authentication, continue it from Recent billing operations.

• Capacity reductions are scheduled for the next renewal and cannot be set below the active people count.
• Unused capacity remains paid through the scheduled reduction date.
• Payment details, billing address, tax IDs, and invoice access are handled through the hosted billing portal; invoice links are requested when needed.

Payment grace and read-only access

After a renewal payment problem, the proposed policy allows a seven-day grace period. If the issue remains unresolved when grace expires, company access becomes restricted/read-only rather than deleting company data. Sign-in, billing review, export, and membership reduction remain available. Restrictions apply server-side, including Slack and queued writes.

Cancel billing, not the company

Use the Cancel at period end control in Company → Billing to schedule an actual subscription cancellation. Review the paid-through date and confirm the action. Cancellation takes effect at period end; it does not delete the company or its work.

• If more than 5 active people remain at cancellation expiry, access is restricted until the company resolves membership or reactivates billing. People are not randomly removed.
• A support request asks for help; it does not cancel billing. A company deletion request is a separate process and is not part of billing cancellation.
• For an invoice, contact, or account question, submit a Support request. A support request is not a billing change. For an actual subscription cancellation, use the authenticated Billing control.

Confirm payments and find receipts

1. 01Prerequisites: be the selected company's owner or billing administrator, verify the financial contact when asked, and check that billing is enabled for this environment. Never enter real card details into a sandbox.
2. 02Review the user-addition approval or quote, including the people, charge due today, recurring amount and expiry. Approve only the intended change. An expired quote needs a fresh review.
3. 03Complete hosted payment if offered. For an authentication-required operation, use Recent billing operations to continue the bank/card authentication. A browser redirect alone is not proof of payment.
4. 04Wait for server-confirmed status and the intended membership change. If declined, abandoned or still pending, inspect the operation before retrying; do not repeatedly confirm the same purchase.
5. 05Review the payment confirmation/history and use its invoice or receipt action, or open the hosted billing portal for available invoices. Invoice links are requested when needed; do not substitute a later invoice for a missing historical receipt.