Table of contents
- Getting Started
- Bookings
- Clients
- Invoicing
- Creating Invoices
- Modifying Invoices
- Updating Invoice Status
- Adding Internal Invoice Notes
- Viewing Invoice History
- Deleting Invoices
- Cloning Invoices
- Merging Invoices
- Printing Invoices
- Emailing Invoices
- Refunding Invoices
- Printing Receipts
- Emailing Receipts
- Quotations
- Online Payments
- Credit Notes
- Manage Invoice Settings
- Printing
- Searching
- Statistics
- Activity Tracker
- Messages, Notes, Watches, and Reminders
- MIDAS Admin Options
- Manage MIDAS
- Manage Appearance Settings
- Manage Booking Settings
- Manage Fields
- Manage Security Settings
- Manage Email Settings
- Manage Print Settings
- Manage Safety Settings
- Manage Invoice Settings
- Manage Database Settings
- Manage Templates
- Manage Public Settings
- Manage Scheduled Tasks
- Manage Miscellaneous Settings
- Check For Updates
- Manage Addons
- Keyboard Shortcuts
- Other Sources Of Support
- About MIDAS
Manage Security Settings
Password Settings
Minimum password length
All users will have to choose a password of at least this number of characters.Force Password Change Every X Days
All users will be required to change their password every X days.Password Reset links are valid for
When a user initiates a password reset request, by default the reset link contained within the subsequent password reset email sent to them is only valid for 2 hours. If the user fails to click the link in their email to reset their password within this time frame, the link expires and the user would need to generate a new password reset request again. This setting allows you to change how long these emailed password reset links remain valid for.Disallow Known Breached Passwords
If enabled, users will not be able to change their password to one which appears in any known public data breach and is therefore considered compromised. This option uses the 3rd party Have I Been Pwned? service. For more information, please see this blog post.Two Factor Authentication (2FA)
Two-Factor Authentication requires all users to sign in with an additional authorization code each time they sign-in with their regular MIDAS credentials.
This helps prevent unauthorized access should a user's MIDAS credentials ever be exposed or compromised.
Enable Two-Factor Authentication for all users?
Enabling this option turns on Two Factor Authentication for all user accounts, using one of the following methods:Authenticator App
Whenever a user signs in to MIDAS, they will need to enter a code displayed on their authenticator app to allow them to complete their sign-in to MIDAS.Device Control
Alert users upon sign-ins from unfamiliar devices
When enabled, whenever a user account is signed into from a new or unfamiliar device, an email notification will be sent to the account holder. The content of this notification may be customized via a template.Session Control
Allow multiple sign-ins for each user?
If selected, each user will be able to be signed in from multiple browsers/devices at the same time. If not selected, a user will only be able to be signed in from one browser/device at any one time. In such instances, signing in from another browser/device will automatically sign out the previous session.Offer users option to stay signed in
If enabled, users will see a "Stay signed in" box on the sign-in screen. If a user then selects this "Stay signed in" box when they next sign in, they will not need to re-enter their credentials the next time they access MIDAS in the same browser.Inactivity leads to sign-out after
Automatically signs out out users if they have been idle for the defined period of time.Include users who opt to stay signed in
When selected, the "Inactivity leads to sign-out after" setting also applies to users who selected the "Stay signed in" option when signing-in. When not selected, users who opted to "Stay signed in" will not have their sessions expire when they are idle.Always force sign-out after
Automatically signs out users after a pre-defined length of time from when they last signed-in. This setting applies regardless of whether a user is active, and regardless of whether they opted to "Stay signed in".Maximum invalid sign-in attempts
To prevent unauthorized access and "brute force" attacks, your MIDAS system can automatically "suspend" accounts if they receive a high volume of consecutive unsuccessful sign-in attempts. Once an account becomes "suspended", the user who owns that account is sent an email from your MIDAS system containing a link allowing them to restore access to their account. Additionally, an administrator user with sufficient privileges can "unlock" a suspended account at any time via the Manage Users & Permissions screen.Allowed IP Range
(Cloud Hosted editions only)For increased security, you can limit who can access your MIDAS sign-in page, based upon their Internet IP address, irrespective of whether they have a valid sign-in for MIDAS.
You can restrict access to a single IP address, or an IP range. This can be useful if MIDAS is hosted on a public web server, which potentially could be accessed by anyone worldwide. MIDAS' "Allowed IP Range" setting can be used to restrict access to users in your own country, organization, or to just you!
IPs are made up of a set of 4 numbers, each ranging from 0-255. These four numbers are each separated by a period (dot) character, and together form an IP address. For reference, MIDAS also displays your current IP address in the security screen.
By default, the "Allowed IP Range" setting in MIDAS is set to *.*.*.*
"*" is a wildcard character, meaning that any value is acceptable. This will not restrict IPs, and will allow access from any IP. You can change this to only allow access from a single IP, by entering the target IP in this box - If you only want to allow access for yourself, simply enter your IP here.
To restrict access to within your own organization / site, you could instead enter something along the lines of "192.168.*.*" - This would allow access to anyone with an IP starting "192.168", so "192.168.2.1" and "192.168.10.200" are examples of IPs that would be allowed.
Rather than use the "*" wildcard character, which will allow any value in the range 0-255, you can instead further limit this to a range of values. For example entering [127-255] would only allow IP's that fell within the 127 to 255 values (inclusive). Example: 172.16.10.[127-255] - Allowed IPs fall in the range 172.16.10.127 - 172.16.10.255