These preferences are global and affect all records, across all OUs:
The company review settings allows admin to enable the company’s review feature found within the Company record and set-up a company review reminder.
To activate the company reviews feature, simply check the ‘Enable Company Approvals’ option.
‘Number of days before Company review task activates’ determines how many days before a Company Review Task’s due date is activated and starts sending out reminder emails.
The currency setting allows admin to set the currency of their system. The currency selected here will be displayed in all of the fields that use a currency within the system.
The Default Watermarks setting allows admin to choose which watermarks are to be added by default to controlled documents within their account. However, each individual OU can be overridden with their own preference using the Organisational Unit Preferences: Watermark settings
Watermarks are added to the system by the iPassport administration team. Should a different watermark be required, contact support at firstname.lastname@example.org.
To select a watermark for a particular area, expand the menu option.
Watermarks are broken down into three elements, all of which are changeable via drop-down lists.
This setting will only apply to new OUs, or documents that do not already have an option set. Changing this setting will not change any individual options already set in the OU settings area.
Organisations have the choice of adopting new minor iPassport updates as soon as they are released. This provides a chance to get familiar with any new features and to start benefitting from them. In some organisations it’s preferable to wait for periodic, major releases which bundle all minor releases since the last major one. Major releases include the traditional validation period, required by some before updates can be allowed.
To accept automatic installation of all minor updates as soon as they are available, tick the checkbox for Rolling Updates.
The Leave Period allows users to set when their leave period begins and when the leave period ends.
The Miscellaneous Settings cover global user settings; these allow admin to set five variables on their iPassport account.
The ‘Disable emailed documents upon download’ setting allows admin to choose if they would like any documents, that they have emailed, to become disabled once the recipient has completed their download. This prevents the recipient from downloading it more than once. This assists in keeping the information secure.
The ‘Send all unrouted mail to account administrator’ tells the system that if a user does not have an email address stored, their emails will be sent to account administrator. This administrator is stored in the parent system so please contact email@example.com for details.
The ‘Enable Simple View’ setting allows you to specify whether simple view should be available or not across the entire account. This is a cut back view of the system, tailored for ease of use by those who are just wanting to complete a task assigned to them or search for content.
The ‘Send support requests to’ allows admin to set the recipient email address for any user using the ‘Contact Support’ button in iPassport. This means support requests can be handled internally. The email address can be a group email address.
The ‘Show Inactive Users in lists’ setting allows admin to either show any user that has been inactivated on the system within all users list, or to have these inactivated users excluded from their system user lists. If the box is checked then inactive user will be displayed in the system user lists.
This setting allows admin to choose what paper sizes they are using as their source documents within iPassport. It is possible to move the control information from the footer (default, and traditional) to the header.
Two factor authentication allows an additional level of security to guard against password theft. When logging into iPassport, in addition to entering a username and password, users will be sent a code via email. Copy and paste this code into the field in order to access the system.
When using two factor authentication, administrators can choose to use code validation each time a user logs in or use the additional code validation to check after a set number of days. For example, admin could ask their users to verify their identity using the email code once a week. The rest of the time they would login normally.
To enable this feature, navigate to Administration -> Settings -> System Settings -> User Logon Settings -> ‘Login Strategy’ dropdown field and select ‘2-Factor Authentication Login’.
Navigate to Administration -> Settings -> System Settings -> Two Factor Settings.
‘Max Attempts’ decides how many times user can incorrectly enter verification code before their account is locked.
‘Remember Second Factor For (days)’ specifies the number of days before the user is asked to provide second factor code again. The user will not have to enter second factor code between logins for this number of days. Only their login and password will be required.
If this value is changed the new settings will only take effect when the original period expires. For example, if this was set to 30 days then users will be asked to enter a second factor code once and then 30 days later and so on. If admin then change this value to 5 days, any user who has already entered a code will not be asked again for 30 days. The new 5 days period will take effect when they are next asked to enter a code.
‘Block re-use of previous password’. Once checked ensures that a user can never use a password that they have previously used within iPassport.
‘Lockout period (in minutes) after maximum failed consecutive logins reached’. If a ‘Maximum consecutive failed login before locking user account’ value is set then admin can define here the time period used to lock the user out, after they failed to login after maximum number of times, before allowing them to try again
‘Login Strategy’ sets which strategy will be used to log users in. This applies to the whole account.
‘Maximum consecutive failed logins before locking user account’ admin can set how many consecutive failed logins a user can perform before being locked out of the system. If a Lockout period is set then the system will unlock the user’s account after this time has passed or admin can unlock the user.
‘Minimum Password Length’ is used to configure the minimum number of characters in a user’s password.
‘Password Expires after (days)’ is used to force users to change their passwords after a given number of days. Use 0 if the password should never expire.
‘Password should include a non alphanumeric character’ forces the user’s password to contain at least one special character (@&<= etc).
‘Password should include a number’ forces a user’s password to contain at least one number.
‘Password should include an uppercase letter’ forces a user to have at least one uppercase letter in their password.
This feature allows setting the rules to automatically define the next version number of a controlled document. A new version number can follow a major revision or a minor revision of a document. iPassport version numbers consist of a major version (the number left of the decimal point) for major revisions and a minor version (the number right of the decimal point) for minor revisions.
The example used here is for COSHH documents; there is a separate section for each type of document (Versioning: Documents, Versioning: SOPs, etc.).
Following popular convention, the version number looks like a real number but it’s not. The decimal point is only a separator between the Major Version and the Minor Version.
The minor version behaves like a natural number so “ver1.01” is the same as “ver1.1” and (with 0.1 increments) “ver1.9” is followed by “ver1.10”, not “ver2.0”.
These steps describe how to set the versioning of COSHH Documents (the same steps apply for all types of documents):
The default value for the First Version Number is 1.0.
To illustrate this element, an SOP could have already reached version 6.3 before it was first added to iPassport. The First Version Number could then be set to 6.3 (if no changes were made), 6.4 (if a minor revision was made) or 7.0 (if a major revision was made).
Numbers entered should avoid trailing zeroes as they are not considered real numbers by the system. This means that the number after the decimal point should be a natural number (1,2,3,...) and not a decimal value like, _01_ or _007_.<br> If trailing zeroes are entered, they will be allowed in this section but they won't pass validation by the system when the document is being authorised.
Minor Revisions will only increment the number to the right of the decimal point. For example, with an interval of 0.5, version 1.9 will be followed by version 1.14 and version 3.5 by version 3.10.
For legacy documents, a version number like 1.01, will be interpreted by the system as version 1.1. Therefore, with an increment interval of 0.1, any existing version 1.01 will progress to version 1.2 when next authorised.
<b>Major Revisions</b> will only increment to the next whole number (the integer left of the decimal point). For example, version _1.0_ will go to _2.0_ and version _3.16_ will go to _4.0_).
The risk settings allow admin to add and edit risk values used in their account. These risk ratings are used in conjunction with the hazard settings (ratings) to generate an overall risk assessment for a SOP (a procedural risk assessment).
A user cannot delete system risk ratings on iPassport QMS.
The risk ratings work by having a ‘Risk Name’ and a ‘Risk Level’. The name is visible when trying to select the risk in the SOP, and the value is used to calculate the risk/ hazard assessment within the SOP.
The value is numeric from 1 – 10 with 1 being the lowest risk and 10 being the highest. An associated value is required for each risk name.
The assessment for each step of the overall risk assessment is calculated by the multiplication of the risk with the hazard to gain an assessment for each level (biological, chemical, mechanical and physical).
For example: an “inevitable” risk has a value of 10, where a risk rating of “unlikely” might have a value of 4. The user can set both the risk name and the level of all new risks.
The hazard ratings are used in conjunction with the risk settings (ratings) to generate a risk assessment for a SOP. The setting allows the user to edit the hazard values used and to add more hazard values.
A user cannot delete system hazard ratings on iPassport QMS.
The hazard ratings work by having a ‘Hazard Name’ and a ‘Hazard Level’. The name is visible when trying to select the hazard in the SOP and the value is used to calculate the hazard/ risk assessment within the SOP.
The value is numeric from 1 – 10 with 1 being the lowest possible hazard and 10 being the highest. An associated value is required for hazard name.
For example: a hazard rating of “none” has a value of 1 or 2, where a hazard name of “death” might have a value of 10. The user can set both the hazard name and the level of all new hazards.
The Index ID Setting allows admin to input the number they would like a record to start counting at. Auto generated indices are generated for documents in the index field by default, but a user can remove this and add one manually by clicking on the cog icon.
By default, these numbers start at 1 and are incremented by 1 for every new record that is created. However, records can start their counting from a predetermined number. Each new record will increment 1 from the starting number.
This is a ‘System Preference’, so applies to all OUs in the account.
If LDAP is already in use for other services it’s very easy to configure iPassport to also authenticate users.
Please contact Genial Compliance- firstname.lastname@example.org before implementing this feature.
Please contact Genial Compliance- email@example.com for more information on this feature.