Skip to main content

Fix Seats and Invite CSV Errors

Most invite problems in the dashboard come from seat limits, unsupported role values, or CSV formatting. This guide uses the real `Users` and `Billing` flows in Blast Audit so you can fix the issue without guessing.

Written by William Karkegi
Updated over 2 weeks ago

Most invite problems in the dashboard come from seat limits, unsupported role values, or CSV formatting. This guide uses the real Users and Billing flows in Blast Audit so you can fix the issue without guessing.

Who this is for

  • Workspace owners managing access in the dashboard

  • Admins sending single or bulk invites

  • Anyone blocked by seat limits or CSV validation messages

Before you begin

  • You may still see Copilot Audit in a few older labels.

  • Open the dashboard pages Users and Billing.

  • For seat changes, you need the Owner role.

  • Remember that pending invitations reduce available seats too.

How to do it

  1. Check seat capacity in Billing.

In Seat management, review Seats purchased, Seats in use, and Active members.

If you need more seats, use Add seats.

If you are above the dashboard cap, the app shows Seat purchases are limited to 100 from the dashboard. Contact sales for larger orders.

  1. Fix blocked seat reductions first.

If you see Lowering seats blocked, remove or disable the required number of users before reducing seats.

The dashboard explicitly says Disable or remove #{{count}} user(s) before lowering seats.

  1. Use the safest path for single invites.

In User management, click Invite people, stay on Single invite, and complete Work email, Role, and Expiration (optional).

Supported roles are Member and Owner.

  1. For bulk invites, start with Download template.

In Bulk upload, use the template instead of building your own CSV.

The bulk form expects columns labeled Email, Role, and Expiration date (optional).

Extra columns are ignored.

  1. Fix the CSV headers if the file is rejected.

If the parser says Include the Email and Role columns in the header row., your header row is missing or renamed incorrectly.

  1. Fix row-level CSV issues.

The dashboard can reject rows for these exact reasons:

  • Email is required.

  • Email format looks invalid.

  • Email can’t start with =, +, -, or @ for security reasons.

  • Role must be Member or Owner.

  • Expiration must be a valid date (use YYYY-MM-DD or your locale format).

  1. Fix seat-overage errors before sending.

If the bulk sheet says Not enough seats, reduce the CSV to the valid headcount, cancel stale pending invites, or buy more seats.

The message will tell you how many people you selected versus how many seats remain.

  1. Send again and review the summary.

A clean run ends with Invitation summary, plus counts for invites created, remaining seats, and any rows that still failed.

Expected result

  • Send invite or Send invites succeeds without validation errors

  • New invites appear under Pending invitations

  • Seat counts in Billing and Users stay aligned with the plan

Avoid this

  • Using roles other than Member or Owner

  • Renaming CSV headers instead of using the template

  • Uploading email cells copied from Excel formulas

  • Forgetting that pending invites consume available seat capacity

  • Trying to change billing as a non-owner

If it still doesn't work

  • Capture the exact validation message or the first few row errors

  • Note your available seat count before retrying

  • Test the same user with Single invite to separate CSV issues from seat or permission issues

  • If the dashboard still fails after a clean template upload, send a support escalation packet with the error text and a redacted CSV example

Practice with sample files

  • Search for Practice Troubleshooting with Sample Documents in this collection.

  • Use the attached PDFs and CSVs there to test this workflow before you use live client files.

Read next

  • Complete Dashboard Onboarding

  • Read the Usage Dashboard

  • Invite Members and Assign Roles

  • Trial, Plan, and Billing Basics

  • Build a Support Escalation Packet

  • Practice Troubleshooting with Sample Documents

Did this answer your question?