Skip to content

Installation

Post-installation

After the wizard finishes, complete these steps so the chosen edition behaves the way you expect.

Last updated Aug 19, 2026 · 2 min read

After the wizard finishes, complete these steps so the chosen edition behaves the way you expect.

1. Sign in

Open /login and use the admin email and password from the installer.

2. Confirm the use case

Go to Dashboard → Settings → Global → Use Case.

It should match what you picked in the installer. Change it here if you need to — you do not reinstall. See Deployment Use Cases.

3. Set the public name and logo

Settings → Global

  • Application name (this is the wordmark on Organization and Personal public sites)
  • Logo and favicon
  • Timezone and language

4. Edition-specific setup

SaaS Platform

  1. Open Workspaces and confirm your default workspace.
  2. Review Subscription Plans (Free, Starter, Professional, Enterprise).
  3. Connect Stripe if workspace owners will pay for plans.
  4. Add professionals (users), set a profession, and mark them available so they appear on /appointment.
  5. Optionally turn on public registration and the Pricing page.

Organization

  1. Invite staff under Users. Assign roles (admin, manager, staff).
  2. Create event types per doctor or staff member.
  3. Add organizations and contacts if you use CRM.
  4. Share /appointment or each person’s /u/{username} link.
  5. Leave registration off unless you want the public to create accounts.

Personal

  1. Create your event types (duration, location, price).
  2. Set weekly hours on each event type.
  3. Share /u/{your-username}. /appointment redirects here.
  4. Connect Google or Outlook calendar if you use them.
  5. Turn on appointment payments in Settings → Payment Configuration if visits are paid.

5. Email

Configure SMTP so confirmations and reminders send. Settings → SMTP (or your mail settings page).

Send a test booking to yourself before going live.

6. Front pages

Install seeded Home / FAQ / Contact / Footer copy for your edition. Edit them under Front Pages.

Changing the use case later does not overwrite pages you already customized.

7. Cron (production)

Point the server cron at Laravel’s scheduler so reminders run:

* * * * * cd /path/to/proschedule && php artisan schedule:run >> /dev/null 2>&1

Included jobs: appointment reminders, high-risk reminders, notification cleanup, calendar sync. SaaS subscription expiry jobs run only when SaaS Platform is on.

8. Demo data (optional)

Only on a throwaway or public demo database:

php artisan command:import_demo

This deletes existing users and loads sample appointments for the current edition. Details: Installation process — demo data.


Related documentation:

← All ProSchedule – Online Appointment Booking Software for Service Businesses documentation

We use cookies to understand how visitors use this site. Cookie Policy