Company Team Accounts

A Company lets a group of customers share billing or shared access without every member needing their own separate purchase.

Joining a company

• The founder — whoever creates the company (typically by leasing an office or starting a shared day-pass setup) is automatically an admin and employee of it.
• Invited members — an admin invites someone by email; they accept from /portal/team, choosing either an employee role or a billing-contact role.

What "employee" actually grants

Being flagged isEmployee on a company is what grants access to that company's shared pools:

• A shared day-pass pack, with a per-employee credit cap the company controls.
• If the company has an active office lease, that lease's shared meeting-room credit pool — but only up to the lease's actual seat capacity. Priority goes to whoever was added earliest (the founder is always first). An employee added beyond the office's physical seat count doesn't get free access to the shared credit pool — they pay for their own day pass to use the space, same as anyone else. Staff can still mark more people as employees than the office seats past that point; it just doesn't grant free perks past capacity.

Billing contacts

A isBillingContact member sees and manages invoices for the whole group; a plain employee sees their own usage but not the group's billing controls. These two flags are independent — a real person can be both, neither, or just one.

Where staff manage this

/admin/customers/[id] lets staff toggle a customer's company role flags directly — useful for fixing a mistake or handling an edge case without going through the invite flow. This is intentionally more permissive than the self-service invite path (which hard-blocks once a lease is at capacity) — staff have a reason to override it sometimes, and the tradeoff is enforced at the point of actually using shared perks, not at the point of being labeled an employee.