Built-in Security Policies

This article details use of security policies. If you are looking for built-in positions refer to the positions list for your system.

Naming conventions

The following naming conventions are in use:

  • "Coordination" — means full access to data with assignment and moving

  • "Officer" — means full access to data without assignment and moving

  • "Basic" — means limited access only to assigned events and/or records

  • "ReadOnly" — means the user cannot write or create

  • "New" — adds the ability to add a new record

  • "Special" — means a custom rule that does not fit any convention

Additionally, the following register group names are used:

  • "recovery" means all the registers in the recovery module

  • "operations" means request, message, offer, log, contact

  • "reference" means "wiki"

Register Permissions Glossary

When viewing configured register security permissions, the following access options are available.

Can access the register

The user can see the register in navigation

Can access a set of items

The user can view lists of items in data grids and lists

Can indirectly update an item

Can edit items that are embedded in sub-forms

Can directly see the register in the user interface

Controls whether this register is included user interfaces such as navigation

Can directly view an item

Can view a full item record in the UI and via the API

Can directly create an item

This controls the "New" button on the UI, and allows top-level items to be created

Can directly edit an item

Controls the "Edit button on the UI, and disallows top-level edits to items

Can assign an item

Can assign items to users, positions and resources

Can add a comment to an item

Can add a note to be added to the history of a record using the yellow comment box

Can move an item between events

Can move items between events including global workspace events.

Can see the unassigned counter

Can see the counter for non-assigned, active records

Can create an item without Register Workflow Restrictions

Can bypass workflow states to set any status code at any time

Last updated

Was this helpful?