In Robin, if your organization has Google SSO and the "Allow personal booking" setting enabled, permissions will work a little differently.
When any Google SSO users reserve rooms in your organization, Robin will always try to create the event as the user first, before:
A. Falling back to the booking account as the organizer if you're using the legacy composer or,
B. Falling back to the space as the organizer if you're using the latest composer.
To avoid problems around rejected meetings, you should make sure users have permission in G Suite to schedule on the room.
If done successfully, you will be the organizer of any event you book via Robin apps instead of needing an invite from the booking account. Keep in mind that impromptu meetings booked from room displays & kiosks will always be from the booking account for security reasons because we can't reliably determine who physically presses the button.
This guide assumes you're using resource calendars.
How to set permissions for personal booking
The easiest way to make sure permissions are valid is to go to your admin panel in Google, then go to Apps > G Suite > Calendars > General settings and check this box if it isn't already:
And then right above that setting you should see "internal sharing options". This is where you'll want to set your resource calendars (secondary calendars) to at least "Only free/busy information", but "Share all information" works too.
This setting may not apply to resources you've already created, so be sure to confirm their sharing settings match the setting above:
Once you've confirmed the settings are in place, you can enable personal booking via Manage > Integrations:
You'll now be the organizer for any new events you create through Robin. Anyone signing in without Google SSO will book via the booking user.
Is your office a shared workspace?
If your office is a shared workplace, any tenants who do not share the domain with the host company will need to book spaces directly through Robin and enabling the "allow personal booking" setting is not recommended in this case-- unless you're okay with allowing outside G suite domains to book on your resource calendars. For more tips on best practices for multi-tenant offices, head this way.