Part of an application where users can create, edit, and view data.
Holds activities where users complete tasks (actions) and view information (views).
|An activity where users evaluate their organization's compliance.|
|A tool or policy that manages a risk.|
|An action that helps mitigate an issue.|
The category of data that appears on an assessment. Dimensions can be custom (similar to a select list) or based upon any relationships or references to the topic or sub-topic.
The non-administrative users who work with Compliance Management and its applications.
A component on a form where a user can input data. Fields can include plain text, numeric, date and time formats, as well as select lists (dropdown menus), and attachments.
|A topic that could impede your organization's ability to remain compliant.|
|Contains your organization's regulatory compliance frameworks and controls for use in assessments.|
A record saved to an object type (the record category). For example, Requirement is the object type, while Ministerial Directives is the object.
The category of the data collected (e.g. control, issue, requirement detail). Once a record is saved to an object type, it becomes an object.
|A directive that your organization must follow in order to maintain compliance.|
The various stages of the assessment process (e.g. Creation, Define Scope of Assessment, In Progress, and Complete) for an assessment workflow.
A collection of users saved to a group (e.g. Compliance Team members or Issue Owners). The user group they are assigned to will determine their rights within the app.
Data entered or selected in a field. For example, Name is the field, but the data entered in that field, John Doe, is the value.
Controls the flow of data as well as defines what data is displayed, where it’s displayed, and to whom it’s displayed through applications, activities, search results, reports, and assignments. Each assessment type has a workflow.