Difference between revisions of "Defining Roles, Permissions and Users"
| Line 4: | Line 4: | ||
TYPICAL IMSMANG Roles | TYPICAL IMSMANG Roles | ||
| + | |||
| + | <center> | ||
| + | {| class="wikitable" width="600" | ||
| + | |- | ||
| + | | align="center" colspan="2" | '''Table 6. Typical IMSMANG Roles''' | ||
| + | |- | ||
| + | | width="300pt" | '''Role''' | ||
| + | | width="300pt" | '''Explanation''' | ||
| + | |- | ||
| + | | align="left" | Data Entry | ||
| + | | align="left" | Users whose primary function is to enter field reports and other data into the system. This role may or may not include the ability to approve field reports. | ||
| + | |- | ||
| + | | align="left" | Data Verification | ||
| + | | align="left" | Users who typically perform quality checks on the data entered by Data Entry users. This role is often responsible for verifying the accuracy of the data entered and approving field reports. | ||
| + | |- | ||
| + | | align="left" | Operations | ||
| + | | align="left" | Users who typically browse for information within IMSMANG to make operational decisions. Operations users may sometimes be grouped by function (for example, MRE, clearance or victim assistance). These users often perform searches for data, generate reports and analyze the data to support operational needs. | ||
| + | |- | ||
| + | | align="left" | System Administrator| align="left" | When printed, a current view provides an excellent summary of all the information known about an item, so it could be the source for many reports. Print each current view before finalizing it to ensure it displays the desired data. | ||
| + | |} | ||
| + | </center> | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 22:15, 19 February 2013
IMSMANG allows information managers to control permissions for IMSMANG functions through the management of users and roles. With multiple permission levels for the Workbench, for example, different users can be assigned different permissions, allowing programmes to implement a data-entry workflow that distinguisheses between data entry and data verification roles. It is recommended to set up a permission structure that reserves approval authority for field reports for the most trusted users.
TYPICAL IMSMANG Roles
| Table 6. Typical IMSMANG Roles | |
| Role | Explanation |
| Data Entry | Users whose primary function is to enter field reports and other data into the system. This role may or may not include the ability to approve field reports. |
| Data Verification | Users who typically perform quality checks on the data entered by Data Entry users. This role is often responsible for verifying the accuracy of the data entered and approving field reports. |
| Operations | Users who typically browse for information within IMSMANG to make operational decisions. Operations users may sometimes be grouped by function (for example, MRE, clearance or victim assistance). These users often perform searches for data, generate reports and analyze the data to support operational needs. |
| System Administrator| align="left" | When printed, a current view provides an excellent summary of all the information known about an item, so it could be the source for many reports. Print each current view before finalizing it to ensure it displays the desired data. | |
| Role | Description |
|---|---|
| Data Entry | Users whose primary function is to enter field reports and other data into the system. This role may or may not include the ability to approve field reports. |
| Data Verification | Users who typically perform quality checks on the data entered by Data Entry users. This role is often responsible for verifying the accuracy of the data entered and approving field reports. |
| Operations | Users who typically browse for information within IMSMANG to make operational decisions. Operations users may sometimes be grouped by function (for example, MRE, clearance or victim assistance). These users often perform searches for data, generate reports and analyze the data to support operational needs. |
| Systems Administrator | Users who perform information management-specific functions such as creating field report templates, designing reports, backing up and restoring data and other technical functions. |
| Guest | Users with essentially read-only access to browse data. |
 |
To add, change permissions associated with, or remove IMSMA roles, you must have access to the Role Admin permission |
Permissions allow a user to view information related to a function, or view and change information related to a function.
Roles are named groups of permissions that can be assigned to users.
IMSMA includes several predefined roles that have one or more permissions assigned to them. The predefined IMSMA roles are Operations, System Administrator, Data Entry, and Guest.
| How To |
|---|
| How To |
|---|
You can use the predefined roles as is, or you can change them to suit your needs. You can also add new roles or copy existing roles. The following sections provide information for performing these actions. The default permissions associated with IMSMA’s predefined roles and their descriptions are listed below:
Table 37. Default Permissions for IMSMA Roles
Role Name Default Permissions Provides Access to... Operations
Operations Base Table Export
Combo Box Mgmt
Country Structure Mgmt
Data Inventory Manager
Field Report
Field Report Approve
Field Report Export
Field Report Import
Field Report Reject
Form Template Design
Handheld
Impact Scoring
Link
Object Obsoletion
Ordnance
Organisations
Places
Published Form Mgmt
Reference System Manager
Reporting
Role Admin
Search
Theme Manager
User Admin Export country structure, explosive ordnance, organisation, and place data.
Add, change, and remove option values.
Add or change country structures and country structure levels.
Add, change, and remove custom defined fields, custom option values, and data categories.
Add, save, submit, and delete field reports.
Approve field reports.
Export field reports.
Import field reports.
Reject field reports.
Add, change, and remove field report templates. Add, change, and remove handheld field report templates.
Add, change, remove, and generate impact scores.
Add links between item records.
Toggle items in the Location View window between active and inactive.
Add, change, and remove explosive ordnance. For this permission, you can also specify read-only access.
Add, change, and remove IMSMA organisations. For this permission, you can also specify read-only access.
Add and change IMSMA places. For this permission, you can also specify read-only access.
Print the results.
Change the status of field reports and export field reports for the handheld.
Add, change, and remove coordinate reference systems used by IMSMA.
Generate reports.
Add, change, and remove roles and assign permissions to roles.
Locate item records that meet specified criteria.
Change IMSMA icons and map themes displayed on the IMSMA Navigation window’s map.
Add, change, and deactivate users.
System Administrator Map Export
Map Import Export a map to an .apm file.
Import a map into IMSMA.
Data Entry
Data Entry Field report
Ordnance (read-only)
Organisations (read-only)
Places (read-only)
Search Add, save, submit, and delete field reports.
View explosive ordnance.
View IMSMA organisations.
View IMSMA places.
Print the results.
Locate item records that meet specified criteria.
Guest Search Locate item records that meet specified criteria.
