In Nora IPLM, Released is the final lifecycle state for items, documents and drawings. When an object reaches the Released state, it is considered finalized, approved, and production-ready.
This state is intentionally governed by stricter control rules to protect data integrity and preserve the continuity of downstream processes such as manufacturing, sourcing, compliance, and change management.
What Happens When an Object Is Released?
Once an item or document is Released:
- The object is locked against structural or content changes
- It represents a controlled and approved data for the organization
- Any further modification must follow a controlled change process such as revisioning or iteration
Released objects are no longer treated as work-in-progress. They become reference points that other objects, structures, and processes rely on.
Access Control in the Released State
Nora IPLM applies state-aware access rights. Permissions differ between editable objects and finalized ones.
As shown in the screenshot for the Contributor role
For non-finalized objects, users may be allowed to:
- Create or disconnect relationships
- Iterate or revise objects
- Change names or metadata
- Modify structure or content
For Released (finalized) objects, permissions are typically limited to:
- Read
- Download
- Export
- Share
Actions that could break traceability or invalidate downstream usage are intentionally restricted.
This separation prevents accidental changes while still allowing teams to consume and reference released data.
Why This Matters
The Released state exists to:
- Protect approved product data
- Prevent unintended structural or attribute changes
- Maintain consistency across BOMs, documents, drawings and related objects
- Support auditability and regulated workflows
- Enforce disciplined lifecycle progression
Instead of blocking progress, these rules guide users toward correct next actions, such as creating a new revision or initiating a change process.
Key Takeaway: Released in Nora IPLM means final, trusted, and controlled.
It signals that an object is ready for use across the organization, while safeguarding it with stricter rules so the overall product lifecycle flow remains intact.
