There are three things you can check to make sure it is configured correctly.

First, on the Headers page, you can make sure header associations are mapped to your ITP template. You do this by selecting Manage associations:

Second, in Project Settings, make sure the ITP is mapped to the form and approved:

Third, within InEight Plan, select Manage ITPs to make sure the component is mapped to an ITP:

For more information, see the following:

• Headers

• Inspection and Test Plans

The below table lists the default system fields that can be transferred from InEight Compliance to InEight Document.

A Task is an assigned activity that requires action to achieve an outcome. At minimum, a task always includes a Title, Description, Responsible Party, Due Date, and a button that Assigns the task. When the person filling out the task clicks on that button, the status is changed to Scheduled. Other question types can be added as well.

Completed tasks can be found on the All Tasks tab. Once the scheduled work is acted upon, and with proper permissions, the status is typically changed to Pending, Canceled, or Complete.

A Form is an activity that provides requested information in predefined fields. Forms can range from very simple and straightforward, to more complex, involving a Form Flow which is a series of actions to be completed in a sequential manner by different people/roles.

Within a Compliance module, when a form is completed it is called an Event. Those completed forms (events) are located in the All Events tab.

When a form or task is created, access is granted in a couple of ways:

• The user’s profile and their role/permission level is the first driver.
• In Suite Administration > Under User Management, the user must be created and at least one Role and Organization/Project must be assigned.

  • For example, an Account Administrator at the Root level will have broad access, whereas a Foreman may only have access for a specific project.

• In Suite Administration > Roles and permissions, the roles are defined as Level 0, 1, 2 or 3.

  • For example, a Level 3 Administrator has access to edit product settings and modules, and Levels 0, 1, and 2 do not.

• At the Module-level, Categories are defined and can be selected for a template. These can be used as permissions to drive security within the module.
• At the Module-level, Roles are created, which drive access to modules, events, templates, settings, and more.
• At the Module-level, once a user’s profile is created in Suite Administration, Roles can be assigned here, by Organization/Project and Category.
• Within a project > module > Settings > Project Settings, the User Group toggle can be turned on and User Groups identified. Identified groups can be associated with desired events/tasks.
• Within a project > module > Templates Manager, and within a Form or Task > Properties, the Organization association drop-down identifies the hierarchy for which the form/task will be visible to users. If an organization checkbox is selected, it will be visible, assuming the user has permission. Category association is also identified on this page.

When completing a form or task:

• Depending on template configuration and user assignments within the module, you can determine whether the user’s name will appear under a People Picker question type.
• When initiating a form flow, and depending on form flow configuration, you may be identified as the Original Reporter or Form Flow Initiator. At other steps in the form flow, based on your role and permission level, you may have continued access to the form if you have been identified by role or by your username as the responsible party for that step.