The software is designed with a hierarchical structure and users are given access to various levels, as determined by their position and responsibilities.

 

The highest level is the Organization.The only people that have access to this level are the Organization level administrator(s).

 

Within your Organization, there are Modules – the next level. A Module is a subgroup which can be thought of as a template for a specific configuration. Because different courses or phases of training within an Organization require unique configurations, we typically build multiple Modules, or templates, for each Organization.

 

The lowest level is the Instance. Instances are measurement periods for a Module, and may be called a “Class” or “Season”. This where all of the data are collected. Each period of data collection is stored within a single Instance; this allows you to monitor trends across Instances.

 

Understanding Module v. Instance

Essentially, the Module is a container for the template from which all of the Instances are built. This template contains all of the documents and settings that were configured for this course. When you create an Instance, any settings and configurations that exist at the Module level will be in that Instance. Once an Instance is created, the Module and the Instances within it are designed to function somewhat independently, so:

 

  • Changes that are made at the Module level will not affect any Instances created prior to the changes.
  • When you make changes at the Instance level, they will not be saved in the Module template. In other words, the changes you make at the Instance level will only live in that Instance. Therefore, it is suggested that any configuration changes be made at the Module level, unless there is a unique circumstance in a particular Instance.
  • To make changes at the Module level, start from the Module Homepage.
  • To make changes at the Instance level, start from the Instance Homepage.

 

Data are collected within an Instance. No data are collected at the Module level, but when an Instance is closed, the statistical data collected within that Instance can be transferred up to the Module level. So, the Module ends up acting as a container for the configuration and all of the data collected across Instances.

 

See also:

About Permissions & Roles

The GideonSoft Data Model

 

= = = = =

Version(s): 17.2 and later