Safety Classification
Overview
SealDoc supports safety classification for documents that require different levels of scrutiny based on risk. Safety classification affects approval rules — higher-risk items can require more signers or stricter separation of duties.
Built-in Schemes
SealDoc provides three industry-standard safety classification schemes:
| Scheme | Standard | Levels |
|---|---|---|
| ASIL | ISO 26262 (Automotive) | QM, ASIL-A, ASIL-B, ASIL-C, ASIL-D |
| DAL | DO-178C (Aerospace) | DAL-E, DAL-D, DAL-C, DAL-B, DAL-A |
| Risk Class | IEC 62304 (Medical) | Class I, Class II, Class III |
Custom Schemes
If your organization uses a different classification scheme, you can define custom levels in Admin Settings. Each custom level has:
- A name (e.g., "Critical", "Major", "Minor")
- An ordering (lowest to highest risk)
- Per-level approval rules
Per-Class Approval Rules
Each safety classification level can have its own approval rules:
| Setting | Description |
|---|---|
| Minimum signers | The number of "Approved" signatures required. Higher-risk levels typically require more approvers. |
| Independence level | The separation of duties required: none, person-level (different user), or department-level (different Jira group). |
For example, you might configure:
- QM — 1 approver, no independence requirement
- ASIL-A/B — 2 approvers, person-level independence
- ASIL-C/D — 3 approvers, department-level independence
Assigning Safety Classification
Safety classification is assigned per document (Jira issue or Confluence page) from the SealDoc panel. Changing the safety classification is logged in the audit trail and may affect the approval requirements for that document.
If the safety classification is changed on a document that is In Review or Approved, SealDoc automatically revokes all active signatures and reverts the document to Draft. This ensures that approvals always reflect the correct safety classification level. The reclassification and revocation are logged in the audit trail.