Skip to main content
Docs / Team management

Team management

How Max team seats work

A Max subscription includes seats for the subscription owner and their invited team members. Everyone on the team uses the same plan entitlements, concurrent-job allowance, and shared optimization usage. Queued and running jobs count toward that shared allowance. If all slots are in use, wait for an existing job to finish or cancel a queued job before submitting another. The owner remains responsible for the subscription and team membership.

Inviting and removing members

The subscription owner can open Account Settings → Subscription to invite people by email, review pending invitations, and remove active members. Teammates sharing an office network can accept their separate invitations; each valid invitation has its own retry limit. Use the email address the invitation was sent to. Removing a member stops their access to the shared subscription but does not restore optimizations they already used in the current billing cycle.

Usage by team member

The same Subscription tab shows how many optimizations each active seat has consumed during the current billing cycle. This breakdown is visible only to the subscription owner. It reconciles to the subscription-wide total that QueryBolt uses for quota enforcement.

Unassigned usage

Usage from before per-seat tracking was introduced, or from a member who has since been removed, appears as Unassigned or former-seat usage. It stays in the shared total until the billing cycle resets, but the former member’s identity is not exposed.

Still stuck?

This page didn’t answer it — the QueryBolt team can help directly.

Contact support