Platform Administration
For VendorStreet platform administrators: cross-organization oversight, market overrides, platform pricing, and system settings.
This page is for VendorStreet platform administrators — the people who operate the platform itself and support the organizations running on it. If you’re an operator running your own markets, venues, or experiences, you want Getting Started instead; nothing here applies to your account.
Platform admin tools sit under /admin and are visible only to users with platform administrator rights.
What can a platform administrator see?
The admin area gives a cross-organization view that ordinary accounts never get:
| Area | What it covers |
|---|---|
Overview (/admin) | Platform-wide dashboard, including a Needs attention panel |
Markets (/admin/markets) | Every market across every organization |
Market detail (/admin/markets/:id) | One market’s info, system status, platform pricing, audit trail, and admin controls |
Organizations (/admin/organizations) | Every organization on the platform |
Vendors (/admin/vendors) | Vendors across organizations |
Bookings (/admin/bookings) | Bookings across organizations |
Invoices (/admin/invoices) | Invoices across organizations |
Payments (/admin/payments) | Payment records and the platform ledger |
Notifications (/admin/notifications) | Outbound notification activity |
System (/admin/system) | Unverified accounts, platform settings, configuration keys, Stripe fee configuration |
What controls are available on a market?
Opening a market in the admin area gives you several panels:
- Market info — the operator’s configuration, viewable without switching accounts.
- System status — the market’s operational and billing state.
- Platform pricing — the per-booking fee for this specific market, overriding the platform default. This is how a negotiated rate is applied. See Payments & Payouts.
- Read-only view — inspect without risk of changing anything.
- Admin controls — status and visibility overrides, billing and onboarding overrides.
- Audit & activity — the change log for the market.
Overrides exist for support and launch assistance: unblocking an operator stuck behind an onboarding step, activating a market for a customer whose payment is being handled outside the normal flow, correcting a status set by mistake.
What’s in System settings?
- Unverified user accounts — accounts that never completed email verification, the usual explanation for “I registered but can’t get in.”
- Platform settings and Configuration keys — platform-wide configuration.
- Stripe annual market fee and Create annual price — the pricing objects behind market activation and subscriptions. See Billing.
Guardrails
Every override is audited. Use them for support and launch assistance, not as a routine way of working.
A few principles worth holding to:
- Prefer the read-only view when you’re only diagnosing. Most support questions are answered by looking.
- Overrides bypass the checks that exist for a reason. A billing override means a market is running without having paid; an onboarding override means a step was skipped. Both are correct occasionally and corrosive as habits.
- Leave a trail. The audit log records what changed, but not why. Note the reason wherever your team tracks support work.
- Platform pricing changes affect real invoices. Confirm the arrangement before applying a per-market fee override.
Next steps
- Payments & Payouts — fee structure and Stripe Connect
- Billing — activation and subscriptions from the operator’s side
- Troubleshooting — common issues to check before overriding anything