An example: a routine confirmation with restricted access
A people team may prepare a routine confirmation letter using approved wording while keeping the employee's record restricted. A manager may need to review one document without receiving access to unrelated correspondence. The final issued copy should be identifiable alongside the appropriate approval record.
Describe these responsibilities before assuming that a shared company folder is suitable. Explain which roles prepare, review and issue letters, where the authoritative employee record sits and how access changes when staff move roles. Use an anonymised process example in an initial enquiry. Employment-related content can require specific confidentiality, retention and procedural decisions. Epistles is intended to support correspondence handling around those decisions; it does not make the employment decision or replace the specialist systems, advisers and policies your organisation uses.
Privacy is part of the service, not an afterthought
Correspondence often contains sensitive personal, financial or business information. Access control, secure transport, protected storage and careful document sharing have to be designed into the workflow from the beginning. Individuals should see only their own records, while organisations should be able to grant carefully scoped access to colleagues.
Public QR verification, analytics and search indexing must not become shortcuts around those restrictions. Retention should reflect legitimate requirements rather than promising to keep everything forever. Customers need clear explanations of how records are stored, who can handle postal fulfilment and what happens when they request deletion or export.