MIDAS :: Manage Users And Permissions

"Manage Users & Permissions" gives you extensive control over user accounts. Use this option to add/remove users, and to control which MIDAS features each user has access to. Active Directory integration can also be enabled and configured from this screen.

There are three tabs on the Manage Users & Permissions screen:
Users - From this tab you can add a new user, remove an existing user, or modify an existing user's details or permissions.
Groups - For this tab you can define a new a new user group, remove an existing user group, or modify the permissions on an existing group.
Single Sign-On (SSO) - From this tab you can configure and enable/disable single sign-on integration with an Active Directory

Adding a New User

Remember: Passwords are case sensitive

If you have enabled Single Sign-On (Active Directory) authentication with the "Update User Permissions upon each authentication" option, user's permissions will be updated whenever they access MIDAS with current permissions from the user group in MIDAS matching their Primary Group in your Active Directory

Cloning (copying) a User

Modifying a User

NOTE: For security, the user's password is not displayed when modifying. Only add text to this field if you wish to change the user's password. Leaving it blank when proceeding to "Save Changes" will leave the user's current password unchanged

If you have enabled Single Sign-On (Active Directory) authentication with the "Update User Permissions upon each authentication" option, user's permissions will be updated whenever they access MIDAS with current permissions from the user group in MIDAS matching their Primary Group in your Active Directory

Removing a User

Only the user will be removed - any bookings made by that user will still remain in MIDAS

If you have enabled Single Sign-On (Active Directory) authentication, removing a user will only be temporary - the next time that user authenticates, they will be added back to MIDAS. In such instances, "Suspending" the user (via the "Account is Suspended" option) rather than removing them, will revoke their access.

Changing/Resetting a User's password

Tip: After entering a new password for the user, before proceeding to "Save Changes", tick the "Auto send User their Login details via email" option to have MIDAS send the new password to the user via email

Forcing a User to change their password at next Login

Suspending/Unlocking a user account

See Also: Managing Security Settings

User Groups

"User Groups" allow you to define a sets of permissions that can then be easily applied to individual user accounts. This saves you from having to manually define each permission for each user at a time. Instead, the "Apply Permissions from Group" drop-down list on the "Users" tab will allow you to quickly update the selected user's permissions with the permissions assigned to a particular user group.

In addition, if you have enabled Single Sign-On (Active Directory) authentication for your MIDAS, User Groups are used to determine the permissions assigned to each user who authenticates via your Active Directory.

In such instances, MIDAS user permissions will be assigned from a MIDAS User Group with the same corresponding name as the user's "Primary Group" name in your Active Directory.

For more information, please refer to the separate Active Directory Integration documentation.

List of Available User and Group Permissions

The following user permissions can be set on a "per user" or user group basis:

SettingDescription
Can Change PasswordAllow/Deny the user the ability to change their password at any time
Note: This option is not applicable to "Group" permissions, and has no affect if you have enabled Single Sign-On (Active Directory) authentication
Can Add BookingsAllow/Deny the user the ability to add new bookings to MIDAS. Available options are:
No - User cannot add any bookings
Yes - User can add new bookings
Requests Only - User can only make booking requests (bookings which must first be approved by a MIDAS user with "Can Process Booking Requests" permission)
Can make Historical BookingsAllow/Deny the user the ability to add bookings for dates earlier than the current date (i.e. in the past) - useful for maintaining accurate booking records.
Can book outside Operating HoursAllow/Deny the user the ability to make bookings which fall outside the normal "Operating Hours" of each venue.
Can Modify BookingsControls how the user can modify bookings. Options are:
No - User cannot modify any bookings
Own Bookings - User can only modify bookings they originally entered
All Bookings - User can modify any booking
Can Delete BookingsControls how the user can remove bookings. Options are:
No - User cannot remove any bookings
Own Bookings - User can only remove bookings they originally entered
All Bookings - User can remove any booking
Can Add ClientsAllow/Deny the user the ability to add new clients to MIDAS
Can Modify ClientsAllow/Deny the user the ability to modify existing clients in MIDAS
Can Delete ClientsAllow/Deny the user the ability to remove existing clients from MIDAS
Can Email ClientsAllow/Deny the user the ability to directly email clients from within MIDAS
Can View Client InfoControls the level of client information displayed to the user. Options are:
No - User cannot see who has made a booking, only that a venue is "Unavailable"
Client/Org Only - User can only see client's names & organizations
Full Info - User can view all client contact info (addresses, phone, fax, etc)
Own Bookings - User will only see booking and client information for their own bookings. Other user's booking's will simply display in the booking grid as "Unavailable" time slots
Can Print (Bookings)Allow/Deny the user the ability to print booking data
Can Print (Emergency Evacuation Data)Allow/Deny the user the ability to instantly print out ongoing bookings at that point in time (Useful in the event of an Emergency, so you can instantly see who is on-site and where)
Can use InvoicingAllow/Deny the user the ability access to MIDAS's Invoicing features. Options are:
No - User has no access to any of the invoicing features
Yes - User has full access to all of the invoicing features
Limited - User may create/generate invoices, but may only view/modify/delete invoices which they created/generated (i.e. they will not have access to invoices added by other users)
Can process Booking RequestsAllow/Deny the user access to "Pending Booking Requests" to approve/reject incoming booking requests
Can use My MessagesAllow/Deny the user use of the "My Messages" feature
Can make Day NotesAllow/Deny the user the ability to attach notes/reminders, viewable by all users, to specific dates. To edit notes; use the main calendar to navigate to the date you wish to add notes to, then click/tap the full date (just above the "Logged in as" line)
Can use Activity trackingAllow/Deny the user use of the "Big Brother" feature - a log of recent activity by MIDAS users
Can use StatisticsAllow/Deny the user to view Statistics and reports about bookings, clients, venues, invoices, resources, and users
Can Restore BookingsAllow/Deny the user the ability to restore recently deleted bookings
Can Manage Booking TypesAllow/Deny the user the ability to add/modify/remove Booking Types
Can Manage ResourcesAllow/Deny the user the ability to add/remove common Resources
Can Manage VenuesAllow/Deny the user the ability to add/modify/remove/group Venues
Can Manage UsersAllow/Deny the user the ability to add/remove users & set user permissions
Can Manage MIDASAllow/Deny the user the ability to manage key MIDAS settings
Can Manage AddonsAllow/Deny the user access to settings for optional addons. For more information on available addons for MIDAS, please see https://mid.as/addons
Is InvisibleControls the level of logging of a user's MIDAS activity. Options are:
No - All user's activity is logged by MIDAS (accessible via "Recent Activity")
Login/Outs Invisible - All user's activity except their logins and outs is recorded
Full Invisibility - Nothing the user does is recorded in the Recent Activity log
Maximum bookings allowedAllows you to limit the total number of bookings the user can add to any individual calendar date or calendar week. Leave blank for no limit
Maximum booking lengthAllows you to limit the maximum length/duration (in minutes) the user can make any single booking for. Leave blank for no limit
View AccessControls which "groups" of venues the user has access to. This can be used to restrict which venues a user has access to and "hide" venues from users. Users will only be able to filter their booking grids by the venue groups for which they have been granted access
Day Starts At X and runs for Y hoursBy default, a day starts at Midnight and runs for 24 hours. If your operations are only 9am - 5pm, for example, you can to restrict MIDAS to only show and allow access to this portion of the day. Alternatively, if you run a night time entertainment venue, with operating hours from 7pm - 3am, setting the "Day starts at" to "19:00" and the "and runs for" setting to "8" hours will then restrict MIDAS to those times
Note: If you restrict a user's hours in this way, the user will only be able to view those hours in the booking grid - they will no longer have access to the multiple day view
Times ListIf "Time Lists" have been setup in your MIDAS, this field will allow you to assign a "Time List" to this user, that is, the list of time periods/durations they will be allowed to select from when making bookings. If set to "None", the user will be presented with standard Start/Finish time selectors

For security, the primary/initial MIDAS user will always have access to manage users and MIDAS and cannot be deleted

Single Sign-On (SSO)

If present, the Single Sign-On (SSO) tab of the "Manage Users & Permissions" screen allows you to enable and configure integration with an Active Directory, allowing users to seamlessly login to MIDAS without having to enter credentials each time.

IMPORTANT: Single Sign-On (SSO) Active Directory support is only available if your MIDAS is "self hosted" AND licensed for "Unlimited" users

For more information, please refer to the separate Active Directory Integration documentation.