One of Skedda's main goals is to help your venue's users help themselves. To this end, you can empower your users to make their own bookings. The nature of the self-service setup depends on how lenient you want to be with granting access to your scheduler, and whether or not online payments are enabled. 

The ability of users to make bookings is determined by the type of access you have selected for your venue.

When the access-type 'Everyone can look and book' is selected, any person with your bookings URL will be able to go directly to your scheduler and make a booking. If the person already has an account they will be directed to login. If they do not already have an account it will be created transparently for them during their first booking.

When the access-type 'Everyone can look, but only those we invite can book' is selected, any person with your bookings URL will be able to go directly to your scheduler and view availability. Only those people with a user account listed as trusted on your users list, however, can make a booking. To do this they will need to login with their trusted user account.

When the access-type 'This is a private venue' is chosen, users need to be on your user list. Those given the access Regular can view availability only. Those given the access Trusted can additionally make bookings. Any person attempting to navigate to your scheduler URL will be forced to login, and only those user accounts on your users list are permitted access in this way.

You may wish to review the following related articles: 

Special note for venues with online payments enabled:

Bookings will be possible by all members of the public (or, in the case of a private-access venue, by just those users in your users list). When a user visits your subdomain they will be able to choose a time on the scheduler and then start the booking process. If they already have an account they will be directed to login. If they do not already have a user account it will be created for them seamlessly during their first booking.

Did this answer your question?