Skip to main content
Was this helpful?

Enterprise Reservation System For Organisation Admins

This walkthrough is for the person who owns the operational setup. You define the organisation boundary, choose who can manage inventory, connect Stripe, and decide which services require payment before confirmation.

Time to complete: 20-30 minutes
Difficulty: Intermediate

Before You Start​

  • Confirm your subscription plan:
    • Store can own 1 active organisation.
    • Enterprise can own up to 5 active organisations.
  • Gather the branding assets you want on the public booking page:
    • organisation name
    • slug
    • logo URL
    • public headline and description
  • Decide the default billing currency for the organisation.

Step 1: Create And Name The Organisation​

  1. Open the organisation workspace.
  2. Create the organisation with its operational name.
  3. Add the slug you want to use in public booking links.
  4. Save the organisation and confirm it becomes available in your organisation switcher.

Why this matters: all resources, reservations, staff memberships, Stripe settings, and MCP scopes are isolated by organisation.

Step 2: Add Members And Assign Roles​

Use organisation roles to keep payment and operational responsibilities clean:

  • assign admins for billing, Stripe, branding, and exports
  • assign editors for resource and resource-type operations
  • assign members for day-to-day reservation creation
  • keep viewers read-only

If one person works across multiple organisations, assign their role separately in each one. Role membership does not leak across organisations.

Step 3: Connect Stripe​

The admin-only Stripe flow is:

  1. Review the onboarding explanation in PrimeCal.
  2. Launch the Stripe onboarding link.
  3. Complete or resume onboarding in Stripe.
  4. Return to PrimeCal and review the connection status.
  5. Confirm the organisation default currency.

In the current frontend, org admins do this from /app/reservations/billing. The same surface is also the Stripe return target for /settings/billing/stripe and /settings/billing/stripe/refresh.

For the step-by-step billing screen and Stripe status guide, use Organisation Billing and Stripe Settings.

PrimeCal stores:

  • stripeAccountId
  • stripeConnectStatus
  • defaultCurrency

PrimeCal does not store card numbers, CVC values, or bank-account details.

If you need to stop charging for new bookings, disconnect Stripe from the same Billing screen. Existing Stripe-side records stay in Stripe for audit and support workflows.

Step 4: Configure Resource Types And Pricing​

For each service, define one resource type and decide whether pricing is active.

Recommended checklist:

  1. Create the resource type.
  2. Add its booking duration and buffer rules.
  3. Set pricingEnabled.
  4. Set paymentRequired if confirmation must wait for successful payment.
  5. Set priceAmount in minor units, such as 2500 for 25.00.
  6. Use the organisation currency by default unless the service needs an approved override.

PrimeCal derives reservation amounts from this resource-type configuration. The client cannot submit its own amount or currency.

For the complete paid-booking confirmation flow, use Paid Bookings.

PrimeCal's organisation-scoped public flow uses the organisation slug and shows:

  • logo
  • public booking headline
  • public booking description
  • available services and resources
  • payment-required messaging

Use branding that makes the public page feel like your organisation, but keep the wording operational. Customers should understand the service, whether they need to pay, and what happens next.

Step 6: Review Audit And Compliance Expectations​

Admins are the right owners for:

  • Stripe connection changes
  • payment configuration changes
  • organisation archival decisions
  • payment-related exports

PrimeCal records audit events for critical billing and reservation payment state changes. When you remove personal data later, keep the minimum legal references required for bookkeeping and dispute handling.

Screenshot References​

StepFileCaption
Create organisationdocs/assets/user-guide/enterprise-reservation-system/admin-create-organisation.pngCreate the organisation once, then use the active-organisation switcher for all later work.
Stripe statusdocs/assets/user-guide/enterprise-reservation-system/admin-stripe-onboarding-status.pngReview the Stripe connection state before you enable payment-required services.
Billing settingsdocs/assets/user-guide/enterprise-reservation-system/admin-billing-settings.pngSave the organisation currency and keep Stripe controls in one admin-only place.
Pricing setupdocs/assets/user-guide/enterprise-reservation-system/admin-resource-type-pricing.pngConfigure price, currency, and whether payment is required at the resource-type level.
Public brandingdocs/assets/user-guide/enterprise-reservation-system/admin-public-booking-branding.pngKeep the public page clear, branded, and honest about payment behavior.

Troubleshooting​

I cannot create another organisation​

Check whether you reached your plan limit. Store supports one active owned organisation. Enterprise supports up to five active owned organisations.

Stripe is connected but payment-required bookings still fail​

Review the organisation Stripe status first. Incomplete onboarding, disabled charges, or missing verification can leave the account connected but not ready to accept live payments.

Editors can change resources but not billing​

That is expected. Billing and payment-related data stay admin-only.