Native Out-of-the-Box (OOTB) datasets

Activity Center draws on native out-of-the-box (OOTB) datasets from several Diligent apps. The following sections describe the available datasets and where the data originates in each app.

Projects app datasets

The following table describes the Projects app datasets available for dashboard creation and where the data is pulled from. Each project within the Projects app has the following tab categories: Dashboard, Planning, Fieldwork, Controls, Reviews, and Issues. The datasets come from data tracked in these tabs and their subtabs and sections.

Projects app dataset Corresponding Projects app data capture
Planning Files

This dataset pulls its data from the Planning Files subtab subset of the Planning tab.

Fieldwork This dataset pulls its data from the Fieldwork tab.
Controls Controls data is managed under the Fieldwork tab. This dataset pulls its data from the Control toggle of the Risk Control Matrix.
Risks

Risks data is managed under the Fieldwork tab. This dataset pulls its data from the Risk toggle of the Risk Control Matrix.

Control Performance

Control performance data is managed under the Fieldwork tab. This dataset pulls its data from the Control performance section of the Walkthrough subtab of a control.

Control Tests Control Tests data is managed under the Fieldwork tab.
Reviews This dataset pulls its data from the Reviews tab.
Issues This dataset pulls its data from the Issues tab.
Todos Todos data is managed under the Issues tab. This dataset pulls its data from the Project to-do Lists section of the To-do subtab.
Requests

Requests data is managed under the Issues tab. This dataset pulls its data from the Request list tracking section of the Requests subtab.

Timesheets Timesheets data is managed under the Issues tab. This dataset pulls its data from the Time & Budget Tracking section of the Timesheets subtab.
Actions This dataset pulls its data from the Actions section of the Follow-up & Remediation subtab which is part of the Issue Details section under the Issues tab.
Certifications This dataset pulls its data from the Certification section of the Dashboard tab.
Projects This dataset pulls its data from the All projects table.

Risk Manager app datasets

The following table describes the connection between Strategy app datasets available for dashboard creation and where the data is pulled from in the Strategy app. Strategy organizes its data around core objects: Risk, Control, Process, and Objective, each with its own fields, custom fields, and relationships to the other objects.

Each object-centric dataset treats one object as the central object. Every other entity included in the dataset relates directly to that central object rather than to another related entity. Each object-centric dataset also honors the row-level security (RLS) of its central object, so users only see rows they are permitted to see based on that object's access rules.

Strategy app dataset Corresponding Strategy app data capture
Risk Centric Dataset

Risk is the central object and includes all of its fields, including custom risk fields. The dataset also includes fields from related Controls, Control Assessments, Issues, Actions, Risk Assessments, and Objectives. These related entities connect directly to Risk rather than to one another. RLS is honored for the Risk object.

Control Centric Dataset

Control is the central object and includes all of its fields, including custom control fields. The dataset also includes fields from related Risks, Control Assessments, Processes, Objectives, Actions, and Issues. These related entities connect directly to Control rather than to one another. RLS is honored for the Control object.

Process Centric Dataset

Process is the central object and includes all of its fields, including custom process fields. The dataset also includes fields from related Strategy objects. These related entities connect directly to Process rather than to one another. RLS is honored for the Process object.

Objective Centric Dataset

Objective is the central object and includes all of its fields, including custom objective fields. The dataset also includes fields from related Strategy objects. These related entities connect directly to Objective rather than to one another. RLS is honored for the Objective object.

Risk Inherent Heatmap Contains the Inherent Impact and Inherent Likelihood fields, along with selected Risk attributes such as Risk Owner and Risk ID. This dataset is purpose-built for creating an inherent risk heatmap.
Risk Likelihood Heatmap Contains the Residual Impact and Residual Likelihood fields, along with selected Risk attributes such as Risk Owner and Risk ID. This dataset is purpose-built for creating a residual risk heatmap.

BoardEffect app datasets

The following table describes the connection between BoardEffectapp datasets available for dashboard creation and where the data is pulled from in the BoardEffect app. Each native dataset corresponds directly to a report that BoardEffect Admins can export as an Excel or CSV file from Site Settings > Reports.

BoardEffect app dataset Corresponding BoardEffect app data capture
Recent Logins This dataset pulls its data from the Recent Logins report under Site Settings > Reports. It contains fields related to the login activity of board members across mobile and web devices, including the date and time of each login, whether the login attempt was successful, and the type of device used.
User Term Information This dataset pulls its data from the User Term Information report under Site Settings > Reports. It contains fields related to each board member's term or service on the board, including their roles, the number of terms served, and terms set to end within the next 12 months.
Attendance Report This dataset pulls its data from the Attendance Report under Site Settings > Reports. It contains fields related to board members' attendance across scheduled meetings, including event name, event time, user details, and attendance status.
Permissions This dataset pulls its data from the Permissions report under Site Settings > Reports. It contains fields related to each board member's application-level permissions within the platform, such as file permissions, messaging, and private directory access.

Policy Manager app datasets

The following table describes the connection between Policy Manager app datasets available for dashboard creation and where the data is pulled from in the Policy Manager app. These native datasets contain metadata about the policy documents managed in Policy Manager and the tasks associated with reviewing and progressing them.

Policy Manager app dataset Corresponding Policy Manager app data capture
Organization Policy Document

This dataset contains metadata about each policy document in the Policy Manager app. It includes:

  • descriptive attributes such as document name, description, category, sub-category, type, version, and tags
  • classification and ownership fields such as target audience, owning group, and owning person
  • lifecycle dates including approved date, publish date, last review date, and next review date
  • status fields such as document status, whether it is in a folder (InFolder), and whether it was created using a template (UsingTemplate)
Organization Policy Document Task

This dataset contains metadata about individual tasks tied to policy documents in the Policy Manager app. It includes:

  • task identifiers and descriptors such as task name, definition name, description, type, and section name, along with assignee details (FirstName and LastName)
  • progression dates such as task active date, checked-out date, due date, and complete date, along with status fields (TaskStatusCd and TaskStatusMeaning)
  • numeric attributes including task due days, order number, and SLA days. The IsPhase field indicates whether the task represents a phase within the document workflow