SLIDE 1
Security Management Security in RiskView The Security functionality - - PowerPoint PPT Presentation
Security Management Security in RiskView The Security functionality - - PowerPoint PPT Presentation
Security Management Security in RiskView The Security functionality allows Users with Admin Group Permissions to: Setup and maintain the Users that can access the system Setup and maintain the Registers that separate the risk data into
SLIDE 2
SLIDE 3
Security in General
Security comprises the following elements
SLIDE 4
Security Workflow Process
1. Setup and maintain Users 2. Setup and maintain Permission Groups 3. Setup and maintain Registers 4. Associate User, Permission Groups and Registers
SLIDE 5
Users are the People that can login to RiskView
Users
Users/People (same thing) are maintained via:
- Admin > People (as general Users see them)
- Security > Users (as Admins see them)
Users are Global, meaning that they are visible throughout the system Person + Username + Password = User
SLIDE 6
View
With View permission, users can
- nly view and print
records, they cannot alter records.
Forms and Permission Groups
Edit
With Edit permission, users can view, print, create, edit and delete records.
Permission Groups can support both View only and Edit access Firstly, all the forms from a module are bound together into a Permission Group
- Action Manager
- Action Viewer
- Assurance Manager
- Assurance Verification Manager
- Assurance Verification Viewer
- Assurance Viewer
- Bowtie Manager
- Bowtie Viewer
- Exception Manager
- Exception Viewer
- Project Manager
- Project Viewer
- Risk Study Manager
- Risk Study Viewer
Standard system include… But Admin users can add their own
SLIDE 7
Permission Groups are comprised of interacting forms
e.g. a Bowtie comprises Risk Scenario, Risk Cause, Risk Consequence and Risk Control forms.
System-Wide permissions apply to the forms that are common across the system
e.g. when a Base Control is created, it can be seen in every register.
Register permissions apply to forms that are specific to a register
e.g. when an Action is only visible in the Register within which it was created.
Background on Permission Groups
Permissions cannot be changed but are made available so that their context and usage can be understood
SLIDE 8
- The Groups shown here are
the standard system Groups and apply to the standard modules.
- You can add your own groups
- r group many groups
together if that makes it easier to manage.
- Each Group can have both
View and Edit permissions to different forms
- Each Group can include other
Groups
Permission Groups
SLIDE 9
Linking Permission Groups and Users to Registers
For Users 1, 2 & 3
As Users 1, 2 & 3 have permissions set at Register 1, they automatically have the same permissions on all the child registers as well
For Users 4 & 5
As Users 4 & 5 have permissions set at Register 1.1, they automatically have the same permissions on all the child registers as well
Important Note
Permissions on Register items apply
- nly to items within that register
e.g. view permission on an Action means that the user can see Action in the specified Register (and its children)
Permissions on Global items apply irrespective of where that item appears
e.g. edit permission on a Base Control has a global effect
SLIDE 10
To give Users permissions within a Register: 1. Select the Register 2. Choose Edit Register 3. Click to Add a new Associated Permissions entry 4. Specify the Name of the Associated Permissions 5. Specify the Users and the Permission Groups having access 6. Press OK to close
Adding a User to a Group of Permissions on a Register
SLIDE 11
Security Workflow Process Summary
1. Setup and maintain Users 2. Setup and maintain Permission Groups 3. Setup and maintain Registers 4. Associate User, Permission Groups and Registers
SLIDE 12
1. Design and implement the Register Structure
Hierarchy based on corporate divisions, projects, locations, etc.
2. Review and fine-tune the default Permissions
Will the permissions/groups give you the flexibility you need going forward
3. Identify the Users and import/setup their details
Importing from Excel can save significant time
4. Map and implement the Users and their required Permissions
A matrix can be a useful tool here
Starting the Process
SLIDE 13
To make it easier to manage the process, RiskView 7.7.1 will have a new View which will bring all the security elements on to one page.
Going Forward…
For each Register, it shows:
- The Users who have permissions
- The Register from which the permissions were set
- The Name of the Associated Permissions entry
- All the Permissions Groups assigned
In the near future, this View will be further enhanced to support editing so all security can be managed on one page.
SLIDE 14