Report module structure

Each standard report is composed of one or more report modules that display data. In turn, each report module is composed of a single parent node (sometimes called a report kind), and 1 or more child nodes (report items), which you define on the Standard Report Modules screen. The parent-child structure of report modules and report items gives you flexibility when designing reports, since you can define several report modules of the same type, assigning each to different roles. You can then create their child report items to show the fields appropriate for those roles. Depending on which user logs in, their report shows only the fields they need.

Parent report modules

A parent report module defines where the report module appears, such as the Profiler Graph report or Invitations Form report. It also defines which roles have access to use that module. For example, the orange box in the following image surrounds the Responses Form Profile section report module, one of several report module for the Responses Form standard report.

Report items

The main purpose of the report item is to define which fields the user sees in the report module. Some report modules need only a single report item. For example, the Responses Form customer name report module defines the header used to identify the customer on the Responses Form report, and needs only one report item to define the field used for that header. Other report modules can use several report items. For example, the orange boxes in the following image surround two separate report items in the Responses Form Profile section report module. One includes several fields in a left-side column, and another includes several different fields in a right-side column.

Role-based permissions

Determine which users can see standard reports in the following ways:

• For most reports (excluding Responses and Satisfaction reports), determine which roles can see specific report modules by associating user roles with report modules on the Reporting > Reports > Standard Report Modules screen. For example, you might want users with different roles to see different Profiler Table report modules. For more information, see Standard Report Modules.
• Additionally, for most standard report types (again excluding Responses and Satisfaction reports), you must determine which roles have the capability to see each standard report type by associating user roles with report capabilities on the Company > Users > Roles > Roles screen. For example, by granting the View Profiler Table capability to a role, you allow users with that role to see Profiler Table reports. For more information, see Roles. Whether the roles you assign capabilities actually see any specific reports of that type is determined by the roles you assigned to the report modules.

• For Responses and Satisfaction reports, determine which roles can see specific report modules by granting access to the parent standard report and the child report modules on the Reporting > Reports > Standard Reports screen. For more information, see Configuring Responses reports in Setup and Configuring Satisfaction reports in Setup.

Control Panel fields

Many standard reports have associated Control Panel fields that help users filter data, as listed in the following table. For more information about filters and the Control Panel, see Filters and controls.