Access and accounts

This is where the credentials live. They belong to the device and apply to all events. What a party does with them is set with the event: under Cloud and e-mail and Pay-per-use.

The split has a practical reason: an event package handed on never contains credentials. Sending an event as a template does not send your Dropbox account with it.

Cloud account#

Dropbox, Google Drive and the RAWCaptureBooth self-hosted server are supported.

Signing in runs through the browser: an assistant opens the provider's authorisation page, access is confirmed there and the code is carried back into the booth.

A base folder can be set as well. Every event creates its own folder underneath, named after its identifier.

Mail access (SMTP)#

The outgoing mail account the booth sends through: host, port, user name, password and encryption (STARTTLS or SSL/TLS). One account for all events.

Payment provider#

Keys and credentials for Stripe or Adyen — one provider account for all events. Leaving the secret key field empty keeps the key already stored.

Amount, trigger and flow of the payment are set with the event.