Intelligent Data Imports

If you’re considering a new room booking system, one of your first concerns will likely be importing data from your current scheduling software.

MIDAS allows you to import bookings and data from a range of applications, and we’re always looking to extend this support.

In our last update, v4.41, we introduced better support for importing bookings from Skedda. This included support for “multi-room” bookings, as well as additional date and time formats.

In v4.42, we’ve introduced several additional improvements to make data imports even smoother.

Automatic Field Detection and Mapping

When importing data MIDAS needs to understand how fields in your source data correspond to fields in your MIDAS system. This process is known as field mapping.

After selecting a file to import, MIDAS offers a preview of your data in a table view. At the top of each column is a drop-down selector. This is used to inform MIDAS of the type of data contained in each column.

Field mapping interface when importing booking data into MIDAS
Field mapping interface when importing booking data into MIDAS

For example, if you’re importing bookings, one column in your source data will contain the room or space name. Setting that column’s drop-down selector to “Venue” ensures the data is imported correctly.

Until now, selecting the correct value from the drop-down selector at the top of each column was a manual process. For v4.42, MIDAS will now try and automatically detect the data in each column and suggest an appropriate value for its drop-down.

Of course, you should still check the drop-down for each column before continuing, but this new ‘auto detection’ feature should make importing data into MIDAS easier.

Support for Importing Split Client Names

In many cases of data import, client names are contained within a single field of data.

For instance, if you’re importing a booking for “Joe Blogs”, it’s likely that there’ll be a single field containing the text “Joe Blogs” in your raw data.

Some booking systems however may split client names across multiple fields when exporting data. There may for example be separate fields for first (given) name and last (surname).

MIDAS typically expects a single field containing the client name, but for v4.42 we’ve added support for instances such as the one described above where names are split across fields.

This improvement makes it easier to migrate to MIDAS from booking systems such as Hallmaster.

Together, these improvements reduce manual setup and make transitioning to MIDAS faster and more efficient.


Bulk Modify User Account Permissions

If you’re familiar with MIDAS booking software you’ll know that it offers an extensive range of access controls and permissions. Permissions can be assigned on a per-user basis. In fact, if you’ve been following our blog, then you’ll have seen that we’re adding 14 new permissions for MIDAS v4.42 too!

We’re now making it easier to apply bulk permission changes across multiple user accounts.

Previous Behavior

In previous versions, when adding or modifying a user account, an “assign permissions from group” drop-down was presented above the various user permissions that could be assigned:

Previous permission assignment method using user groups in MIDAS
Previous permission assignment method using user groups in MIDAS

This was a great way to quickly copy the current permissions from a user group to an individual user account.

However, this was a one-time action. MIDAS would snapshot the selected user group’s current permissions and apply them to the individual user account. Any subsequent changes to the group’s permissions would not affect existing user accounts.

Introducing Permission Inheritance

So we have re-worked this for MIDAS v4.42. The “Assign permissions from group” selector has been removed and replaced by a new role-based “Inherit Permissions from” selector.

When a user account is set to inherit permissions from a user group, any subsequent changes to that group’s permissions will automatically apply to all linked user accounts.

User account inheriting permissions from a user group in MIDAS v4.42
User account inheriting permissions from a user group in MIDAS v4.42

This now allows you to bulk modify user account permissions with ease!

When to use manual permissions

If you still want to grant or revoke individual permissions on a per-account basis, you can – simply set the “Inherit Permissions from” option to “[None]”. When you do this, MIDAS will display the complete list of current permissions for that user, allowing you to make individual changes as required.

User accounts set to ‘[None]’ will not be affected by changes to any user group permissions.

While this new feature may not be all that significant for customers with only a handful of user accounts, larger organizations with several hundred users will benefit greatly from the ability to modify user permissions in bulk.


Expanded Administrative Permissions in MIDAS v4.42

Administrators appreciate the extensive range of permissions that can be assigned on an account-by-account basis in their MIDAS booking software.

These allow the creation of anything from fully privileged administrative accounts to ones with very limited “view only” permissions, and everything in between.

To provide administrators with even greater control, we’ve extended the range of available permissions for MIDAS v4.42 to now include 14 additional administrative permissions.

New granular administrative permissions in MIDAS v4.42
New granular administrative permissions in MIDAS v4.42

These new permissions replace the previous “Can Manage MIDAS” permission. This generic permission controlled whether a user was able to access the “Manage MIDAS” configuration screens.

Over time the “Manage MIDAS” screens have grown to include a vast array of options and settings. These screens allowed users to change email settings, update templates, configure scheduled tasks, tweak invoice or database settings, and much more.

For v4.42, we have split up the old “Manage MIDAS” screen into separate sections. Access to each section is now controlled by its own dedicated permission. This means, for instance, that you can grant permission to a user to be able to modify your templates, but not allow them to adjust the email settings of your MIDAS system.

The 14 new administrative permissions added in v4.42 are:

When updating from an earlier version to v4.42, any user account which held the “Can Manage MIDAS” permission will automatically be granted all 14 of the new administrative permissions during the update.

Administrators can then refine access for each user account via MIDAS Admin Options → Users.

These changes, together with the ability to make bulk permission changes, provide administrators with significantly greater flexibility and control over who can access specific system settings.


Zero Configuration Email Delivery for Cloud-Hosted Customers

Zero Configuration Email Delivery

The ability to send email is essential for any booking system.

From booking confirmations and reminders, to invoices, notifications, and password resets, booking and scheduling systems rely on email.

MIDAS naturally supports the sending of email, but we’ve made some exciting and significant improvements to email sending for our cloud-hosted customers for v4.42.

But first, let’s look at the existing ways in which MIDAS can send email.

Until now, the sending of email by MIDAS has been through a choice between “Sendmail” or “SMTP”.

What is Sendmail?

Available on Linux-based servers, Sendmail is a built-in server application for sending email directly from the server itself. Read more about Sendmail.

What is SMTP?

SMTP (or Simple Mail Transfer Protocol) is the standard language used by computers to send emails across the internet. Read more about SMTP.

Sendmail vs SMTP

Both Sendmail and SMTP options have been available in both our cloud-hosted and self-hosted editions.

“Sendmail” has long been the default ‘out of the box’ email transport setting for cloud-hosted customers. However, we’ve always encouraged customers to move over to SMTP as soon as possible.

That’s because generally email deliverability rates are substantially higher when MIDAS is configured to send email through a customer’s own SMTP server, than if instead sent directly through our own servers.

Whilst Sendmail is configured to work ‘out of the box’ for cloud-hosted customers, SMTP requires a little more configuration.

To configure MIDAS to send email via SMTP, you will need:

  • The address of your SMTP server
  • The correct port number
  • The SMTP username and password
  • The correct SSL, TLS, or STARTTLS encryption method setting

You will also need to ensure that your SMTP server accepts connections from your cloud-hosted MIDAS system. In addition, your organization’s domain must be configured to allow MIDAS to send email on behalf of your domain.

This requires significant configuration and setup. We want to simplify this for our cloud-hosted customers. That’s why we’re introducing cloud email sending.

Introducing “Cloud Sending”

New Zero Configuration Email Sending Option
New Zero Configuration Email Sending Option

For MIDAS v4.42, we’ve introduced a new “Cloud” option for sending email. This new option is available to all cloud-hosted customers, and replaces the previous “Sendmail” option. (Sendmail continues to remain an option for self-hosted customers).

With the new cloud email option selected, you won’t need to specify an SMTP host, or enter credentials or specify ports – MIDAS will take care of all of that!

We have partnered with a dedicated transactional email provider specializing in high-deliverability email delivery services, to provide efficient and reliable email delivery for cloud-hosted customers who select the “Cloud” email sending option.

Zero Configuration Email Sending

To complement our new “cloud” email offering, we’ve also included a “Zero Configuration” option.

With this option enabled, MIDAS and Mailgun will seamlessly handle email delivery for your MIDAS system. You won’t need to configure an outgoing email address, nor will you need to update your organization’s domain’s SPF (Sender Policy Framework) DNS record – email will just ‘work’ right out of the box.

Of course, if you wish to customize the “send from” or “reply to” addresses, you can untick the “Zero Configuration” option and change those settings.

But in its simplest form, our new “cloud” email sending and “Zero Configuration” options mean that brand new cloud-hosted email systems can now reliably send email right from the outset.

Migrating from Sendmail to Cloud email sending

For our existing cloud-hosted customers, if you’re currently using the “Sendmail” option in your MIDAS system, you’ll be automatically migrated to “cloud” sending soon after we update you to v4.42.

If you do not wish to use the new “Cloud” sending option, you should update your MIDAS settings to instead send email via SMTP.

You can change your MIDAS email settings via MIDAS Admin Options → Manage MIDAS → Email.

If your cloud-hosted MIDAS system is currently configured to send email via SMTP, this setting will be unaffected when we update your booking system to v4.42. Of course, you can then always change over to use the cloud email sending option at any time.