Listed below are terms used in UDBapp along with definitions. Various regions sometimes use different terms to refer to the same concept. To maintain consistency, UDBapp uses a uniform set of terms across the app. The list below is intended to provide clarity and connect a diversity of terms to their UDBapp equivalents.
Administrator (Admin)
The highest level of user for UDBapp
By default, all permissions and app features are enabled
Administrators can manage participant access and permissions using various settings and Smart Access Sets
Can create Groups and Subgroups
Administrators join Subjects using an Admin password
Arc account
A unified account used to access all Arc apps (UDBapp, Beam, Geo, and StrideTV)
You can use your Arc account to join multiple organizations and groups
Arc accounts are not deleted when a license expires or is removed
drill — aka “song” or "charts"
The visual composition of a pageantry activity (marching band, indoor guard, etc.) wherein performer coordinates and prop elements are plotted out on a grid system.
For UDBapp, the term "drill" refers specifically to the file that is managed and distributed within the app.
Group
The middle level of organization within UDBapp, contained within a Subject
Examples of Groups are ensembles such as “Marching Band”, “Pep Band”, or “Winter Guard”
Subgroups are created within Groups
Users can join multiple Groups
To join a Group, you must first be a part of its Subject and Organization
Participant profiles are Group-specific
Only Administrators can edit Group properties
license — aka "seat"
Access to each Arc product is handled by purchasing a number of annual licenses
Arc accounts are not deleted when a license expires or is removed
Licenses are managed by Administrators and can be removed from participants at any time to be redistributed to others as needed
In order to join a Group, the account needs to have an available license for the selected product
page — aka “set” or “chart”
The “snapshots” within drill that align with music to create checkpoints for clarity and teaching purposes.
For UDBapp, the term "page" refers specifically to the delineations created from the Pyware® drill file and viewed within the app.
Drill pages, including dot placement, counts, and numbers, cannot be edited within UDBapp
participant
The term for any user of UDBapp that is not an Administrator
Members and Staff join Subjects and Groups as participants using codes
By default, permissions for certain app features are limited for participants
Administrators can change Group-specific participant roles
More access can be granted to participants using Smart Access Sets
Pyware® file — aka “drill file”
The drill file that is exported from Pyware® and then imported into the app
The term drill refers to the file that is already within UDBapp and accessible in the Drill Library
Smart Access Sets
A feature that allows Administrators to grant elevated privileges to selected participants (Members or Staff)
Can be used to allow a section leader or drum major to create shared layer Field Notes or change attendance counts
Subgroup
The lowest level of organization within UDBapp, contained with a Group
Examples of Subgroups are instrument sections such as “Flutes” or “Front Ensemble”, student leadership groups like “Section Leaders”, or responsibility groups like "Prop Crew"
Participants can join multiple Subgroups
Only Administrators can create Subgroups
Subject
The highest level of organization within UDBapp, such as a school, university, or organization
Groups are created within Subjects by Administrators
Users can join multiple Subjects
Subjects are tied to a single organization
Only Administrators can edit Subject properties
Some profile information is shared between Groups in the same Subject