BookingSG Self help
  • Links
    • BookingSG
    • Book a discussion with us!
    • Drop us a note!
  • FREQUENTLY ASKED QUESTIONS
    • 👀About BookingSG
    • ✨Onboarding
      • Sign Up
      • Fees and Charges
      • Onboarding Duration
      • BookingSG Structure
        • Organisation
        • Service
        • Service Provider
      • Different user roles
        • Creating Users Accounts
      • Approval Workflows
      • Login Authentication
      • Send Notification
        • Email Notification
          • Slots - recurring & one-off
          • Events
          • Proxy
          • Email Reminders Notifications
        • SMS Notification
          • SMS Reminder Notifications
      • Customisation
    • 🔗Integration with BookingSG
      • Pre-requisites
      • BookingSG server authentication
      • API listing
        • DEL
        • GET
        • PATCH
        • POST
        • PUT
  • Admin User Guide
    • ✏️Setting up user accounts
    • ⚙️Configure Service Settings
    • 🎨Customising
      • Dynamic Fields
      • Email Notification Templates
      • SMS Notification Templates
    • 🗓️Create timeslots
      • Setting Recurring Schedule
      • Customise Recurrent Schedules
      • Adhoc Timeslots
      • Indicating unavailability
  • SUPPORT
    • 🛠️Staging and production system support
Powered by GitBook
On this page
  1. FREQUENTLY ASKED QUESTIONS
  2. Onboarding

Different user roles

Understanding different user roles

Role
User Access
Login creation

Administrators

Agency /

Organisation Admin (OA)

Mandatory

Administrators

Service Admin (SA)

Optional, as long as there are OA created to oversee

Administrators

Service Provider Admin (SPA)

Optional, created to manage SP, especially if they are non-login SPs.

Administrators

Service Provider (SP)

Mandatory, but optional login access creation for non-human resources - if non-login, can manage with SPA or other admin rights.

End User

Applicants

Authentication either by Mobile+OTP, Singpass or Corppass. Set up by admins during onboarding.

Organisation Admin (OA)

Highest level of admin rights and able to see information across all service(s), including all calendars and availabilities (slots).

Service Admin (SA)

View and manage availabilities and bookings on Service level. Configure Service settings assigned to the SA. Able to view calendars for Service Providers under the Service.

Service Provider Admin (SPA)

Optional user access which can be created under specific Service(s). Useful if external vendors are required to view/accept bookings, especially if Service Providers are non-login accounts.

Service Provider (SP)

Users accepting and taking on bookings. Can be a login or non-login* account, which will be individually assigned a calendar for availability indication.

*Such as rooms or tickets. These can be managed by a Service Admin or Service Provider Admin (SPA).

Reference

PreviousService ProviderNextCreating Users Accounts

Last updated 1 year ago

✨
Creating Users Accounts
✏️Setting up user accounts