Access to the Omni Solution is managed by adding an Omni Permission to a User's Profile.
You are able to create specific Omni Permission Groups in your Channel's Security section.
This article lists the available Omni Permissions and describes what they allow.
The Omni Permissions can be found in Account/Security/Permissions
In the Solution dropdown, select Omni:
You will be able to see the Permissions available for Omni Solution:
The Omni Permissions, and what they do
Digital Services: Access Digital Services Panel
This permission controls visibility (and use) of the Digital Services Dashboard in Omni:
None
| If you set None for this Permission, the Digital Services Dashboard will not be visible on screen for a User when they login to Omni eg  |
Edit
| If you set Edit for this Permission, the Digital Services Dashboard will be visible and available for a User when they login to Omni. This User will be able to order and interact with the services eg:  |
View
| If you set View for this Permission, the Digital Services Dashboard will be visible to the User when they login to Omni, however the User will not be able to order and interact with the services (the controls will not be enabled) |
Menu: Omni Communication Access
This Permission will enable Omni Menu access in the Simpology Manager Menu Ribbon in Solutions:
If you do not add this Permission for a User, that User will not be able to access Omni via the Menu Ribbon when they are logged in to Simpology Manager.
Omni application: Access all applications in my channel
This Permission means that a logged in User in Omni will be able to see all Omni application records. You will generally want to set this to YES for your Assessor users.
Omni application: Access all applications in my entity
This Permission means that a logged in User in Omni will be able to see all Omni application records that belong to that User's entity. This setting is relevant where you are going to invite brokers into Omni to be able to participate in assessment activities. If you set this permission to YES, it will mean that a broker will be able to see the Omni records of applications submitted by their co-brokers within that brokerage.
Omni application: Access reporting documents
This permission controls visibility (and use) of the Reporting Dashboard in Omni:
The Reporting functionality allows you to generate (print) any forms that you might want to create in an assessment process (eg Approval Letters, Assessment Summaries)
Omni application: Allowed to view Access Seeker documents
This Permission will control if the logged in user can see the outcome of an Access Seeker Service. Note that Lender Users should not be able to see Access Seeker reports - so this would generally be set to NO for any of your direct Lender users.
Omni application: Can edit condition
This permission will mean that the User is able to Edit a Condition of Approval that has previously been created in an Omni record.
Where Can edit Condition Permission is YES | When the User is in the Assessment Module of an Omni record, and opens an existing Condition of Approval, an EDIT button will be available and they will be able to update the details of the Condition:  |
Where Can edit Condition Permission is No | When the User is in the Assessment Module of an Omni record, and opens an existing Condition of Approval, the EDIT button will NOT be available:  |
Omni application: Can request applicant for information request
This permission will mean that the User will be able to send a Missing Information Request directly to an applicant.
Where Can request applicant for Information Request Permission is YES | When the User is working in Omni and raises an Information Request, they will have the option to send the Info Request to an Applicant:  |
Where Can request applicant for Information Request Permission is NO | When the User is working in Omni and raises an Information Request, they will NOT have the option to send the Info Request to an Applicant:  |
Omni application: Delete assessment summary note of other user
A User with this Permission will be have the ability to delete an Assessment Summary note that another User has created.
(Note that a User is generally able to delete their own notes)
Where Delete assessment summary note of other user Permission is YES | When the User is working in the Assessment Module and is in the Assessment Summary, the Delete icon will be available on another person's summary note. When they hover over the Delete icon of someone else's note, they will be able to press and delete the note:  |
Where Delete assessment summary note of other user Permission is NO | When the User is working in the Assessment Module and is in the Assessment Summary, when they hover over the Delete icon of someone else's note, they will NOT be able to press and delete the note:  |
User's own notes | The User will be able to delete their own notes regardless of this permission |
Omni application: Edit action item
A User with this Permission will have the Edit button enabled in any Action Item that they open. This will mean that they can Edit the details of this task on this particular Omni application record (ie it will not edit the Master configuration of the Action item)
Where Edit Action Item Permission is YES | When the User is working in Omni and opens any Action Item in the Omni workflow, they will have an Edit button visible on screen:  A typical reason that you might want to Edit this individual Action item might be that you want to change it from Optional to Mandatory for this Omni record, or change who is responsible for the item. |
Where Edit Action Item Permission is NO | When the User is working in Omni and opens any Action Item in the Omni workflow, they will NOT have an Edit button visible on screen:  |
Omni application: Edit Checklist item
A User with this Permission will be able to add a Checklist to an action item that they are working on.
Where Edit Checklist Item Permission is YES | When the User is working in Omni and opens any Action Item in the Omni workflow, they will have the Add Checklist functionality available:  |
Where Edit Checklist Item Permission is NO | When the User is working in Omni and opens any Action Item in the Omni workflow, they will NOT have the Add Checklist functionality available:  |
Omni application: Manage assessment process structure
A User with the Permission will be able to Delete a Process in the Assessment Module section of an Omni record. You might want to do this if you want to remove a double-up or start a fresh one.
Where Manage assessment process structure Permission is YES | When the User is working in Omni Assessment Module, the "delete process" button will be visible and enabled:  |
Where Manage assessment process structure Permission is NO | When the User is working in Omni Assessment Module, the "delete process" button will NOT be visible:  |
Omni application: Raise information request
A User with this Permission will have the button to create an Info Request in their Omni workflows, in order to send a request to an external party (eg Broker or Applicant) to provide more detail or documents for the assessment.
Where Raise Information Request Permission is YES | When the User is working in the Omni workflows, they will have the "Info Request" button available to them in various places in Omni. It will mean that they can create new Info Requests.  |
Where Raise Information Request Permission is No | When the User is working in the Omni workflows, they will NOT have the "Info Request" button available to them in various places in Omni. It will mean that they will NOT be able to create new Info Requests.  |
Omni application: Reassign tasks to another person
A User with this Permission will be able to re-assign all open/outstanding tasks of Person A to another person. This is useful if (eg) Person A goes on holidays or leaves the company.
Where Reassign tasks to another person Permission is YES | When the User has this Permission they are able to see the 'Reassign' button in the all-records filter for a particular person:  |
Where Reassign tasks to another person Permission is NO | When the User does not have this Permission the 'Reassign' button will not be visible to them to perform this function  |
Omni application: Skip mandatory action item
A user with this Permission will be able to skip an action item (task) that is otherwise set to be mandatory.
Where Skip mandatory action item Permission is YES | When the User has this Permission they are able to skip an otherwise mandatory action item (task). This is a senior permission that allows the User to override the usual requirements of an assessment process:  |
Where Skip mandatory action item Permission is NO | When the User does not have this Permission they are not able to skip a mandatory action item (task). If they try to complete a Process without completing all the mandatory items, they will get an error message that they do not have this permission:  |
Omni application: Submit application to lender
This Permission gives the User the right to submit the finalised/approved application into the Lender's core banking platform OR x-channel submit to a wholesale funder.
Where Submit application to Lender Permission is YES | When the User has this Permission they will have the Submit Application button visible in their Omni interface; and when the Omni record gets to the correct status, the Submit button will be enabled:  |
Where Submit application to Lender Permission is NO | When the User does not have this Permission they will not have the Submit Application button visible in their Omni interface; and will not have the ability to submit the finalised application data to the Core system or x-channel to the funder:  |
Omni application: View other entities users
This permission gives the User the ability to 'see' the registered Users of other 'entities'.
For context, a User will belong to an Entity.
An Assessor will belong to an entity (in this case, it would be the lender)
A Broker will belong to an entity (eg their brokerage)
This permission allows a person in one entity to be able to 'see' people in other entities, and they will be able to assign tasks to those people in different entities. This permission is useful if you want to be able to assign Omni tasks to (eg) brokers.