Module Summary

Module Summary

The module summary allows account administrators to view or change the module name and description, set the module to active or inactive, and configure automatic user assignments. The active and inactive choice gives you the ability to turn off the module for the entire InEight product portfolio, per organization or project. Each module is self-contained and does not share information with the other modules. The changes made to a module will be shown throughout the product portfolio, module page, tabs, landing page and mobile device.

Step by Step — Module Summary Navigation

  1. From the Settings page, select Compliance from the left panel.

    • The Product Settings page shows. Select the Module Settings tab.

  2. Select a module.

    The Module summary tab opens.

Configurations

To configure additional settings, click the links in the Configurations list. Each configuration shows in a dialog box.

Alternate Hierarchy

An alternate hierarchy is separate from the default organization and project hierarchy in the InEight cloud platform. You can set up an alternate hierarchy if you need to share templates and user permissions across projects that do not follow the default hierarchy. For example, if your default hierarchy is organized into legal entities for financial reporting purposes, you can create an alternate hierarchy based on project locations. A project in the Infrastructure division might need to share templates and user permissions with a project in the Energy division because both are in the Western region.

To set up an alternate hierarchy, you must perform the following three general steps:

  1. Define hierarchy attributes at the organization level.
  2. Associate hierarchy attributes at the project level with other projects or organizations.
  3. Extend templates and user permissions between future child projects or organizations via hierarchy attributes in Compliance organization settings.

The following Step by Step details how to define hierarchy attributes at the organization level.

Step by Step — Define Alternate Hierarchy Attributes

  1. At the organization level, go to Settings > General > Attribute Definitions.

  2. Click the Add icon.

    • The Add attribute side panel opens

  3. Enter the required fields.

    For hierarchy purposes, the Data type field is most often set to Text or Data. When the type is set to Data, you must select a Data source of either Organization or Project.

    In the example of a location-based hierarchy, an attribute might be named Region, Data type set to Data, Data source set to Organization, and Category set to Location, which lets you associate organizations with regions.

  4. Click Save.

The following Step by Step details how to associate hierarchy attributes at the project level.

Step by Step — Associate Alternate Hierarchy Attributes

  1. Open the main menu at the top of any page, and then click All projects & organizations.
  2. Select the check box to the left of the project you want to use, and then click the Edit icon.

  3. Open the Attributes tab.

    • The Attributes tab opens with each defined attribute organized by category

  4. For each attribute that you want to associate, select an organization from its drop-down list or enter a project ID in its field, depending on the attribute’s data source.

    In the example of a location-based hierarchy, you might associate an attribute named Region with an organization that represents the Western region. If you set this association in a project in the Infrastructure division of your default hierarchy, you are saying that project is also part of the Western region in an alternate location-based hierarchy.

  5. Click Save.

The following Step by Step details how to extend templates and user permissions between future child projects or organizations via alternate hierarchy.

To view or edit Alternate hierarchy settings, you must have a Level 3 access role.

Step by Step — Apply Alternate Hierarchy to Compliance Templates and User Permissions

  1. At the organization level, go to Settings > Compliance.
  2. Open a module’s Module summary tab.

  3. Click Alternate hierarchy in the Configurations menu.

    The Alternate hierarchy dialog box shows

  4. Select attributes from the drop-down lists for template associations and user permissions.

    Template associations and user permissions are applied to all future child organizations or projects of the attributes you select. If you remove the attributes, the associations themselves are not removed.

    In the example of a location-based hierarchy, if you add the Region attribute to these fields, for projects that are both associated with the Western region, templates and user permissions will be automatically assigned to users in future children of the Western region organization.

Automatic User Assignments

The Automatic user assignments configuration lets you save administrative setup time and automatically assign a Compliance role and categories to all users from InEight Platform.

To automatically assign a role, select a role from the drop-down menu.

To automatically assign categories, start typing a category name in the field or click inside the field and select one from the drop-down list.

When you are done assigning roles and categories, click Save.

You must have a Level 3 access role to see and change this configuration.

Language Settings

To show translations of a module's user-configurable fields in different languages, select a language from the drop-down list.

To apply translations to a template, use the import function in a template's Properties tab. See Template Translation for more information.

Module Organization 

Module organization allows you to exclude any project or organizations from certain or all modules, therefore you will not see the project or organization in the module. This is done by moving the project or organization to the right panel. If you exclude a project, the project cannot be used in user assignments or templates.

For example, if you are working on a JV project and they are using a different software to keep track of Safety data, you would want to exclude them from the list of projects.

Step by Step — Module Organization

  1. Select Module organization from the Configurations menu.

    The Module organization dialog box shows

  2. Expand an organization level.
  3. Select the check box to the left of a project to exclude.

  4. Click Save.

    • A Saved Successfully message briefly shows
    • Now that organization is excluded from the module
      • You can view all excluded organizations or projects by toggling the button labeled View Excluded Jobs.


Reporting Tags

Reporting tags are used to secure information when you use reports. Reporting tags drive permissions when running reports. If a question is assigned a reporting tag and you are not assigned that reporting tag in Compliance, you cannot see the response to the question in a report. Reporting tags are defined per module. After you add reporting tags in this section, you can assign reporting tags to users and template questions to define who can see reporting data on those questions.