View source for BPC RiskManager Client - Add new users

=Introduction=


As BPC RiskManager supports multiple access and security models there are multiple ways that new users can be added to a database using the Risk Manager client.  The method you will use depends on your security model.  Broadly they fall into three groups:

* Automatic  (relevent only in single user installs where access rights are assumed, or trusted access models where the operating system login in trusted)
* Operating system secured (relevant where LDAP or NT Groups security is enabled)
* Locally secured (relevant where "locally secured in application" access model is used and operating system logins are not trusted - this is the most common scenario)


We will look at each of these later in this article.


In addition there are four types of user groups maintained by the system:

* Resources
* RiskManager users
* SurveyManager users
* Survey Respondents


Each of these four groups are independently managed inside the system, but the BPC RiskManager client substantially (but not completely) hides this from you. The RiskManager user group has further subdivisions which we will discuss shortly.


Firstly we will consider the four types of users, and then look at how these users are created.



=Types of RiskManager Users=


==Resources==


The resource is the minimum / lowest type of user known to the risk system.  Every other type of risk user is at least a "resource".  


Strictly speaking a resource is NOT a user of the riskmanager client directly.  This user can not access the client, but can receive emails and alerts from riskmanager, be assigned tasks and responsibilities and be tracked in other ways.  


A resource has a unique id assigned automatically by risk manager, but kept invisible from all users, has a first and last name and an email address and therefore is known by the application.



==RiskManager Users==

a RiskManager User must first be a resource, before they can be promoted to a user.  Users have access to the RiskManager client in some degree.  Users may be:

* Restricted (able to access only specific risk domains/organisational units), or 
* Unrestricted (able to access all areas)


In addition a user has assigned roles which are one of:

* Reader/Inquirer  (can only read the information to which they have access)
* Contributor/Risk Owner (can add or change information about risks, etc to which they have access)
* Risk Coordinator (can add information about risks) 
* Risk Manager (can manage risks for one or more risk domains/organisational areas and create new risks)
* Administrator (has the power of a risk manager plus can create users and change application configuration)
* Auditor (can review risks and create audit assessments and has access to specialist audit functionality).



==SurveyManager Users & Respondents==

SurveyManager users are able to access the surveymanager capabilities, and therefore create surveys and review survey results.  Within the riskmanager client these are usually RiskManagers, but if the specialist SurveyManager client is used there is substantially greater surveymanagement capability available.


SurveyManager users have various roles which are defined at both the database and indivudal organisational levels:

* Super (a super user can do anything the system supports)
* SurveyManager (grants the power to create and issue surveys at the organisational level - which depending on the organisational structure established may cover a region of organisation units)
* Dataentry User (can enter data on behalf of other users - such as where paper or phone based data collection is used)
* User (a survey respondent - can only respond to surveys to which they are invited)


==Synching of SurveyManager and RiskManager Users==

A simplified surveymanager interface is built into the RiskManager client.  The user creation and access functions automatically create survey users and roles as required.  With this interface a limited range of surveymanager capabilities are provided, but the surveymanager roles and personnel are synched with the riskmanager roles as follows:


<table border=1 >
<tr>
<th> Survey Manager Role</th><th> Risk Manager Role</th>
</tr>
<tr>
<td>Super</td><td>Administrator</td>
</tr>
<tr>
<td>SurveyManager</td><td>Risk Manager</td>
</tr>
<tr>
<td>Data Entry User</td><td>Not used</td>
</tr>
<tr>
<td>User / Respondent</td><td>Resource</td>
</tr>
</table>


As a consequence of the way users and roles are managed within the application suite, you can use the advanced SurveyManager clients (web and windows) interchangeably with the RiskManager client to manage the surveys.  Most needs are covered by the RiskManager client, but where advanced survey layouts are desired, one of the more advanced survey manager clients may be appropriate.


=Creating Resources and Users in BPC RiskManager=

Resources and users can be created individually or in bulk within the system.  A user must also/first be a resource, so a user is created as a resource first, and then granted access rights as a user.


Resources have no access rights within BPC RiskManager, but can receive emails, reminders, surveys, workflow tasks, etc.


Users have access rights using the BPC RiskManager client.  These rights range from read only access to specific risks up to full administration of the entire system.


Depending on your configuration settings, Resources can be created on the fly.  Administrators can also create and update both Resources and Users can using the security administration windows, both individually or in bulk:

* [[BPC RiskManager - Creating and Updating Resources]]
* [[BPC RiskManager - Creating and Updating Users]]
* [[BPC RiskManager - Creating and Resetting User Passwords]]


=Updating your user preferences in BPC RiskManager=

Various user details can also be set or updated on a per user basis by the individual user.  These include your password, spell checker, screen colour coding, screen resoultion handling, etc.

* [[BPC RiskManager - Updating Your Personal Preferences]]



=BackLinks=

{{#dpl: linksto={{FULLPAGENAME}} }}