Skip to content
English
  • There are no suggestions because the search field is empty.

Installation and Configuration Guide

Overview

This Application Installation and Configuration Guide is designed to assist with the preparation of the customer's instance to enable the V-Resilience Physical Security Management application components to function properly. The document contains configuration steps required after installing the application and describes all application dependencies.

Application Dependencies

Plugins:

  • Configuration Management (CMDB) - com.snc.cmdb
  • System Import Sets - com.glide.system_import_set
  • Task table schema - com.glide.task
  • Explicit Roles - com.glide.explicit_roles
  • CMDB CI Class Models - sn_cmdb_ci_class

Application Access

In order to install the application, a user must have the out of the box role "admin".

The following roles are available for application users:

  • x_vres_app.physical_security_administrator (full access)
  • x_vres_app.physical_security_agent (operations access)
  • x_vres_app.security_integration_admin
  • x_vres_app.assessment_admin

Application Access Requirements

To access and use any functionality of the Bearing Application scoped application, a user must be explicitly assigned the application role: x_vres_app.physical_security_agent or higher. This role acts as a security gatekeeper for the entire application.

Even users with the platform admin role will not be able to view, configure, or interact with the application unless the bearing role is also granted. This enforcement is intentional and ensures that only authorized users can interact with the data, configuration, and logic contained within the application.

External Systems Connection

Scripted REST Service:

Name API ID Comments
Everbrdige everbridge Everbridge Webhook

Scripted REST Resources:

Name Resource Path Method
Process Event /api/x_vres_app/everbridge/ createEvent POST

Flow REST Actions:

Name Comment
Acre - Import Access Levels Imports access level definitions from Acre Security into ServiceNow for synchronization.
Acre Security - Import User Access Lvl  Imports individual user access level assignments from Acre Security into ServiceNow.
Acre Security - Import People  Imports personnel records from Acre Security, including user identity and profile data.
Everbridge - Import Assets Imports asset records (e.g., locations) from Everbridge for operational awareness.
Everbridge - Import Contacts Imports contact details from Everbridge
Acre Security - Remove Access Level to User  Removes specific access level assignments from users based on data from Acre Security.
Acre Security - Add Access Level to User Adds access level assignments to users based on incoming Acre Security data.
Acre Security - User Access Lvls Import  Full import of user-to-access level mapping from Acre Security.
Acre Security - People Import Used for Data Source import.
Acre Security - Access Levels Import Used for Data Source import.

Configure an External Integration

Use the Integrations page in the Security Operation Workspace to configure external system connections such as Acre Security or Everbridge.

Before You Begin

Ensure that the user performing this action has the following roles:

  •  x_vres_app.security_integration_admin
  • x_vres_app.physical_security_administrator

Note: Users without these roles cannot view or configure integrations, even if they have the admin role.

Procedure

  • Navigate to Bearing Application > Security Operation Workspace > Configurations > Integrations.
  •  On the Integrations tab, locate the integration you want to configure.
    • Example: Acre Security or Everbridge.
  • Click Add Connection in the card for the selected integration
  • In the Connection configuration form, enter the required API credentials provided by the external system.
    • Typical fields may include:
      • API endpoint URL
      • Client ID and Client Secret
      • Access token or credentials
  • Click Submit to save the connection details.

Result

The integration status changes from Not Configured to Active, and the system is ready to exchange data with the external service.

  • Tip: After submitting, test the connection or run an import to validate configuration success.

Configuration Instructions

After purchase, the application is added to the Application Manager automatically. Follow these steps to install and configure:

Procedure:

  • Navigate to All > System Applications > All Available Applications > All
  • Find "Bearing Application" using the filter criteria
  • Select the version and click Install After the application has been installed it is ready to use and no further configuration is needed.

Manual Role Assignment

After installing the application, you need to assign additional system roles to the custom application roles manually. This step is required for proper application functionality.

Role Assignments Required:

  • x_vres_app.assessment_admin
    • Add role: assessment_admin
  • x_vres_app.physical_security_administrator
    • Add roles: fd_read_flows, import_admin
  • x_vres_app.physical_security_agent
    • Add roles: user_criteria_admin, canvas_user, email_composer, workspace_user, cmdb_read, service_viewer, sla_manager

To assign these roles:

  • Navigate to System Security > Users and Groups > Roles
  • Search for each custom role listed above
  • Open the role record
  • In the Contains Roles related list, add the specified system roles
  • Save the changes

This manual assignment ensures that users with these custom roles have the necessary permissions to access all application features properly.Testing the configuration

It is recommended to:

  • Install in a development/test instance first
  • Configure test workflows for each core function
  • Clone to production after validation

Demo Data

The application comes with pre-configured:

  • Incident categories and subcategories
  • Standard workflow templates
  • Report templates
  • Dashboard configurations

Support and Troubleshooting

Please use ServiceNow OOB debugging tools and approaches. For any issues contact the Bearing support team.

Common troubleshooting steps:

  • Verify role assignments
  • Validate workflow configurations
  • Review system logs

Service Level Agreement Definition

Customers will be instructed to contact the integration provider (your organization) for technical support. If a customer first contacts ServiceNow Customer Support, then ServiceNow Customer Support will isolate the problem and instruct the customer to resolve the issue with your organization.

  • Support Hours of Operation: 9am - 6pm EST
  • Support Days of Operation: Monday - Friday (exception US Holidays)
  • Expected Call Response Time: Severity level 1: 8 business hours , L2: 8 business hours , L3: 4 business hours
  • Expected Call Resolution Time: Varies depending on the issue severity
  • Contact Method: email
  • Contact Details: support@getyourbearing.com