Security, confidentiality, and access governance
Multi-tiered security roles, four-level confidentiality classification, departmental isolation, statutory retention, and audit logging.
1. Overview & Business Value#
This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for Security, confidentiality, and access governance within SmartERP.
Enterprise correspondence frequently carries sensitive commercial information, classified state correspondence, executive personnel decisions, or legal disputes. SmartERP Letter & Correspondence Management implements multi-tier role-based access control (RBAC), confidentiality clearances, departmental record rules, and audit logging to protect organizational privacy.
{screenshot:security-and-confidentiality-overview-dashboard}
2. Prerequisites & Security Access Groups#
- Required Modules:
smarterp_letter, smarterp_correspondence - Security Groups:
Letter Registry Clerk(Technical ID:smarterp_letter.group_letter_clerk)Executive Reviewer(Technical ID:smarterp_letter.group_letter_reviewer)Director General(Technical ID:smarterp_letter.group_letter_executive)
- Master Data Dependencies: Dual calendar templates (Ethiopian & Gregorian), official stamp repository, letter reference numbering formats, and departmental dispatch routes.
3. Step-by-Step Configuration & Execution#
Step 1: Navigating to the Module Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher (grid icon in the top-left corner).
- Select the Correspondence app icon.
- From the top navigation bar, open Correspondence → Letters → Inbound / Outbound / Internal Memoranda.
{screenshot:security-and-confidentiality-app-switcher-navigation}
Step 2: Creating and Parameterizing Records#
- Click the New button in the top-left control panel.
- Complete the mandatory fields in the record form:
- Letter Subject (Mandatory): Clear administrative or commercial subject heading
- Sender / Recipient Entity (Mandatory): External institution or internal department
- Dispatch Channel (Mandatory): Physical courier, hand delivery, or digital dispatch
- Dual Date (EC & GC) (Mandatory): Official Ethiopian calendar and Gregorian dates
- Configure optional operational parameters and localized tags as required:
- Digital Signature / Seal (Optional): Authorized executive cryptographic stamp
- Security Classification (Optional): Routine, Confidential, Secret, or Top Secret
- Related Prior Reference (Optional): Cross-referenced correspondence tracking ID
- Click the Save icon in the control bar to commit the record.
{screenshot:security-and-confidentiality-record-creation-form}
Step 3: Validating and Processing Transactions#
- State Transitions: Execute operational state progression (Draft Memo → Editorial Review → Legal Clearance → Executive Signature & Stamp → Dispatched / Archived).
- Ledger & System Impact: Maintains immutable institutional correspondence registry with cryptographic QR validation for external party verification.
- Audit Verification: Automated recording of author ID, timestamp, and immutable revision history.
{screenshot:security-and-confidentiality-transaction-processing-state}
Security user groups#
SmartERP Letters defines fine-grained security groups structured across operational responsibilities:
| Security Group | Technical Identifier | Intended Users | Permissions & Access Scope |
|---|---|---|---|
| Letter User | group_letter_user | All standard employees | View public/internal circulars and letters assigned to them; create internal draft memos. |
| Letter Officer | group_letter_officer | Departmental action officers | Create, edit, and submit letters within their own department; view department correspondence. |
| Letter Approver | group_letter_approver | Department heads & managers | Review, approve, reject, or request revisions on departmental letters; endorse circulars. |
| Registry Officer | group_letter_registry | Central mailroom / registry clerks | Access incoming and outgoing registry books; allocate official reference numbers; record dispatch and return receipts. |
| Letter Manager | group_letter_manager | Registry directors & operations managers | Configure numbering schemes, manage templates, maintain stamp registry, and reassign stalled letters across all departments. |
| Confidential Clearance | group_letter_confidential | Executives, legal counsel, HR managers | View correspondence classified as confidential. |
| Secret Clearance | group_letter_secret | Board members, CEO, Chief Legal Officer | View correspondence classified as secret / restricted. |
| Letter Auditor | group_letter_auditor | Compliance officers, internal auditors | Read-only access to all letter audit logs, cryptographic digests, and dispatch manifests across the enterprise. |
Confidentiality levels and record rules#
Every correspondence record is assigned a confidentiality level that strictly restricts database queries via Odoo Record Rules:
flowchart TD
PUB[Public: Visible to all internal users and circular portal]
INT[Internal: Visible to originating department members and recipients]
CONF[Confidential: Requires 'Confidential Clearance' group OR explicit assignment]
SEC[Secret / Restricted: Requires 'Secret Clearance' AND explicit assignment]
PUB --> INT
INT --> CONF
CONF --> SEC
Access Matrix by Confidentiality Level#
| Level | Technical Key | Visible To | Searchable by General Users? |
|---|---|---|---|
| Public | public | All enterprise employees | Yes |
| Internal | internal | Members of the originating department, drafter, assigned reviewers, and recipient partners | Only within authorized departments |
| Confidential | confidential | Drafter, assigned approvers, and users with group_letter_confidential | No (hidden from general queries) |
| Secret / Restricted | secret | Explicitly named participants with group_letter_secret | No (hidden from all non-cleared users) |
Statutory retention schedules and legal holds#
- Statutory Retention Policies: Letters can be bound to automated retention policies (e.g., Financial correspondence: 10 years; Routine circulars: 3 years; Board resolutions: Permanent). When retention expires, letters are marked for archival review.
- Legal Holds: When litigation or regulatory audits occur, authorized compliance officers can place an official Legal Hold on a letter thread. While on legal hold:
- The letter cannot be archived, soft-deleted, or purged.
- Any attempt to alter underlying DMS attachments raises an immediate security block.
- All access events are recorded in high-fidelity compliance logs.
4. Advanced Configuration Points#
- Automated Actions & Scheduled Tasks (Crons):
Letters: Check dispatch delivery receipt status(smarterp_letter.ir_cron_dispatch_check): Runs daily to verify courier delivery confirmation slipsLetters: Follow-up on pending memorandum actions(smarterp_letter.ir_cron_followup): Runs weekly to alert assigned officers of pending correspondence replies
- Custom Print Templates & Reports:
- Official Letterhead Dispatch Copy with QR Verification
- Institutional Letter Inward/Outward Registry Ledger
- Multi-Company Rules: Record-level security isolation under Company 1 (
Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.
5. Comprehensive Troubleshooting Matrix#
| Error Symptom / Exception | Probable Root Cause | Corrective Action / Resolution |
|---|---|---|
Signature Block: Missing executive stamp clearance | Letter cannot be dispatched without authorized cryptographic stamp. | Submit letter to Executive Office for digital signing. |
Calendar Error: Invalid Ethiopian date conversion | Specified Ethiopian calendar date does not match leap year rules (Pagume 5/6). | Use the automated calendar picker to ensure synchronized EC/GC conversion. |
Unregistered Recipient: Partner profile missing TIN | External institutional recipient lacks complete corporate profile. | Create or update recipient partner master record before dispatching. |