Kindhearted Operations software
Log in Create account
Documentation ยท Booking

Booking Setup Overview

What this does

This overview explains what needs to be in place before Booking works as a full operational app.

Booking has its own large settings surface, but some of the most important setup still begins in the Admin App.

It also does not end inside Booking. The work collected here can flow into Timecards, hand customer and project context into Invoice, and rely on cleaner customer records from CRM.

What must already be set up

  • the company must have an active Booking subscription
  • the user must be assigned access to Booking
  • company structure in the Admin App should already be in place if bookings are meant to flow into labor, wages, teams, or downstream apps
  • if the customer-facing side will take payments, Stripe should already be configured
  • if you want branded customer-facing links, domains should already be configured
  • if bookings should reuse shared customer, account, contact, or address records, those records should already be reasonably clean in CRM

Why the Admin App matters here

If you are in Booking and looking for app access, public host setup, or shared payment-provider setup, those items are managed in the Admin App.

That matters because:

  • customer-facing links may depend on domain setup from the Admin App
  • payment collection may depend on Stripe setup from the Admin App
  • staff access may depend on app assignment from the Admin App
  • downstream workflows can depend on the shared company structure from the Admin App

Why CRM, Timecards, and Invoice also matter here

If the same job should keep its context as it moves through the suite, Booking needs to stay aligned with the apps around it.

That matters because:

  • CRM can provide the customer, account, contact, and address records used during booking and job setup
  • Timecards can follow the work created here when labor should not be rebuilt by hand later
  • Invoice can follow the same operational context when billing is created from the work

What you can set up inside Booking

Once the shared setup is in place, Booking has its own app-specific setup such as:

  • forms
  • links
  • imports
  • workflow
  • scheduling
  • payments
  • notifications
  • customer portal behavior
  • custom domain behavior inside the app
  • taxes
  • permissions

Recommended setup order

  1. Finish shared setup in the Admin App.
  2. Assign the right people access to Booking.
  3. Configure Booking settings, forms, workflow, and scheduling.
  4. Test the public, customer, and staff surfaces.

What stays incomplete if skipped

If app assignment is missing, users cannot get into Booking.

If Stripe or domains are missing, customer-facing payment and portal flows may not behave as expected.

If customer and account records are messy upstream, the team can still create bookings, but the same context becomes harder to carry cleanly into jobs, billing, and customer communication later.

Related guides