Clear responsibilities.
A record at every step.
Who handles the request? Which version was approved? What happens after delivery? These questions shape the operational and document workflows in this case.
SUNHEIR OS and the SUNHEIR document center are separate applications. The document center has its own accounts and storage and is not integrated with OS.
SUNHEIR OS
From request to acceptance.
An operations workspace for projects, tasks and approvals. Its service desk gives a request a responsible person, a delivery date and an explicit acceptance step.
Workflow
Request
Submit a service need within the relevant business scope.
Assign & work
Confirm the handler and delivery date, then start the work.
Deliver
Record a delivery note and the selected file versions.
Accept or return
The requester or administrator records acceptance or returns the work with a note.
Responsibilities
- Operations & review
- Handlers carry out work; designated approvers act at the current approval stage.
- Access
- Administrator, operator, finance and viewer roles are refined by business and module permissions.
What stays on record
Formal references pin an approved file version. A new upload does not replace it. A project or task handover changes responsibility only when the named recipient accepts; a changed record requires a new handover.
SUNHEIR document center
From draft to issued original.
An independent workspace for template-based documents, review, seal images, issuance and verification. Editable drafts and issued PDFs have different roles.
Workflow
Draft
Choose a template, edit and save a revision; preview PDF or export a Word draft.
Review
Route the saved revision through sequential or parallel review; return it for changes when needed.
Issue
An administrator issues the approved revision as a numbered PDF with a verification QR code.
Verify
Check the current status and compare a received PDF using its locally computed SHA-256 fingerprint.
Responsibilities
- Creator & reviewer
- Creators prepare documents. Assigned reviewers handle review; department and document permissions govern visibility.
- Administrator
- Manages templates and seal versions and issues approved documents. Direct approval is a separate, reasoned action recorded in the history.
What stays on record
Approval binds the revision, template, rendering resources and selected seal version. Issued originals are preserved; changes require a new revision and issuance. Revocation or replacement remains visible in verification status.
Website editorial controls
A deliberate public boundary.
The separate SUNHEIR website build selects public fields from editorial source content. Internal review notes stay outside the browser package. An indexable build requires editorial approval and valid publication dates.
These are website build controls, not an automated publishing connection to either application. An email preview lets visitors send an inquiry from their own email app; it does not claim that a message was sent.
Built scope, stated precisely.
- Implementation & rollout
- Scope reviewed: SUNHEIR OS 0.4.0 source and document center 2.6.0 documentation and code. Local changes do not establish live release or full multi-user acceptance.
- Connections
- The document center remains independent. This case does not establish live third-party integrations or automated payments.
- Verification & evidence
- A PDF fingerprint compares digital bytes; it does not authenticate paper or provide a certificate-backed digital signature. No efficiency figures or production security certification are claimed.