Where the card goes.

One card, in one place, owned by one person. This is the owner's path — what has to be set up before anything can be bought, and what the system does when it is not.

Travel

1. Put a card on file.

   Admin → Subscription & Billing → Travel bookings. The owner does this, and it is the only place in the product a card is entered. Nobody books a flight by handing their own card to a producer.

2. Approve the ticket.

   A booking is worked up against the show and the traveller before anything is bought. What you approve is what gets ticketed, on the card you linked, for the fare that was in front of you.

3. No card, no ticket.

   Without one, nothing is quietly held, deferred or ordered on account. The product says Card needs linked to book. and stops there. That is the whole behaviour — there is no second path.

4. Demo companies never ticket.

   A company set up to try the product runs against sample offers. The planner works, the itinerary fills in, the confirmation is marked on its face as the sample it is — and no money moves and no seat is bought. You cannot buy a real fare by accident while you are looking around.

Seats and invoicing

Your company's own subscription lives in that same admin, under the same heading, in front of the same person — what the company is on, who is holding a seat, and the invoices that have been raised against it. It is deliberately not a second console somewhere else: an owner who has just linked a card for travel should not have to learn a different screen to see what the workspace itself costs. If you want the figure for your company, ask us and a person will answer — tell us what you are running and we will come back with it in writing.