Explore a standard’s document structure, inspect type properties and open the documents belonging to a selected type.
Product location: /qms/{standardCode}/document-types (fallback: /qms/standards)
Open the standard's Document Types page and confirm its breadcrumb and standard code. The product location uses that code, such as ISO-9001. You need View documents permission to load the structure.
Use the hierarchy to understand the relationships between active types. Open Document Type settings when a type's name, description, flags or active state needs to change.
For example, a standard can have Manual and Template as roots, with Policy and SOP beneath Manual, and Work Instruction, Form, Record and Checklist beneath SOP. Your organisation's configured hierarchy determines its actual types and relationships.
Product location: /qms/{standardCode}/document-types (fallback: /qms/standards)
Use a parent's arrow to show or hide its children. Expand All opens every branch; Collapse All returns to the roots. These actions change the view rather than the configuration.
The root count describes top-level nodes. A structure with two roots can contain many more child types. Expand a branch when locating a particular type instead of interpreting the visible row count as the total configuration.
Select a type's row to open its detail panel. Confirm the selected name and description before reviewing its properties or navigating to documents. Use the branch arrow separately when changing the tree's expansion; expanding or collapsing keeps the selected type and its detail panel.
Product location: /qms/{standardCode}/document-types (fallback: /qms/standards)
Display | Meaning |
|---|---|
REQ / Required | The type is configured as required. Check its actual documents and their review status separately. |
SINGLE / No (Singleton) | Allow Multiple is off for the selected type. |
Level | The type's depth in the hierarchy, counted from Level 1 for a root type; Document Types settings uses the same numbering. Read it together with its parent and children. When the type's display name has been changed, the detail header also shows its stable type name. |
Description | The selected type's purpose; the full detail can be longer than its tree label. |
Allow Multiple | Whether the type is configured for several documents. |
Hierarchy Order | The configured order among the relevant nodes. |
Documents / Templates | Associated records to inspect when reviewing use and impact. |
The flags describe configuration. They do not establish that required content exists, that a document has been approved or that a requirement is satisfied.
For a selected SOP type, review its description and related documents to distinguish it from a policy or detailed work instruction. Use the structure to choose the appropriate class for new work.
Product location: /qms/{standardCode}/document-types (fallback: /qms/standards). Select the intended type, choose View Documents of This Type, and confirm the standard and type filter in the destination.
Choose View Documents of This Type from the selected type's details. The standard's Documents page opens with the banner Showing N document(s) of type TYPE. and lists only that type. For an inactive type the banner adds that the type is inactive. For a form type it shows Forms are managed on the Forms page with Open Forms, and when the type cannot be found it shows The linked document type was not found and lists nothing. Confirm the type and standard before opening or creating a record.
Choose Show all documents in the banner to remove the type filter. Back to Documents on the hierarchy page opens the unfiltered standard document workspace. In its table view, the type selector narrows the list, and All Types restores it. The By type view groups the standard's documents by classification.
Follow the dedicated Forms workspace for form-design and response workflows where applicable. A document's type, its workflow and permission to its content all matter when choosing the next action.
An agent can navigate through the hierarchy and use the selected record's action. Use accessible type identifiers from the current tenant when forming a filtered link; never substitute a screenshot's synthetic identifier.
Product location: /qms/{standardCode}/document-types (fallback: /qms/standards)
If the hierarchy is empty, check that the intended standard is enabled, its document setup is ready and loading succeeded. Review inactive types in settings when looking for a type that was deactivated.
If a selected type has no matching documents, the banner reports Showing 0 document(s) for that type. Confirm the standard and type, then decide whether a new document is needed. An empty type, a type that cannot be found and a failed load are different conditions.
After a type is renamed, deactivated or restored, reload the hierarchy and review the same record. Reopen its associated documents as needed. Expanding or collapsing the tree does not alter those records.
If loading fails, restore the session, access or service connection and retry. Use the selected type's name, standard and product location when asking an administrator to review a configuration issue.
