Tracking progress: statuses
A file’s five statuses (approved, signed, in production, delivered, rejected), the default 'no status' state, and how to set them.
2 min read
Every file carries a status showing where it stands in its lifecycle. A status is always a human decision or a fact: it’s never set automatically on upload. A freshly imported file is therefore "No status", and stays that way until someone decides.
The five statuses
| Status | What it means |
|---|---|
| Approved | The file is approved, good to move forward. |
| eIDAS signed | An electronic signature has been completed on the file. |
| In production | The part has moved into manufacturing at the shop. |
| Delivered | The deliverable has been handed to the customer. |
| Rejected | The file is rejected and needs rework. |
The No status state isn’t a sixth status: it’s simply the absence of a decision, the default state of every imported file.
Setting a status
Two paths, depending on how you work:
- From the file: in the inspector, the Approve and Reject buttons set the corresponding status. You decide once per version: both buttons are only available while the current version has no status. They’re reserved for people with the approve permission.
- From the Kanban view: drag a file’s card from one column to another to change its status. Dropping it in the "No status" column resets the file.
A new version starts with no status
A status applies to the content someone actually reviewed. As soon as a new version is uploaded, the file therefore goes back to No status: the decision has to be made again on the new content. An approved file doesn’t stay "Approved" on a version nobody has looked at, and a rejected file can be reworked and decided on again.
The same rule applies to a drawing made in Comiror: each new publication creates a version, and the drawing starts again with no status.
The "eIDAS signed" case
This status is never set by hand. It appears automatically as soon as an electronic signature request completes on the file’s current version. A signature completed on an earlier version stays attached to that version as evidence, but doesn’t change the status. The "eIDAS signed" Kanban column doesn’t accept a manual drop: it fills itself in. To start a signature, see the guide Approve and sign a drawing.
Was this guide helpful?