Who can read a page
Public, customer, partner and internal pages, and how the site and the API keep them apart.
1. Overview & Business Value#
This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for Who can read a page within SmartERP.

Documentation is often not meant for everyone: a partner price list, a customer runbook, an internal procedure. Every section and every page has a visibility, and the server enforces it on every path that serves a page.
2. Prerequisites & Security Access Groups#
- Required Modules:
smarterp_docs - Security Groups:
Technical Documentation Architect(Technical ID:base.group_system)Enterprise User(Technical ID:base.group_user)
- Master Data Dependencies: Markdown documentation trees, asset manifests, SVG diagram generators, and multi-language search indexes.
3. Step-by-Step Configuration & Execution#
Step 1: Navigating to the Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher (grid icon in the top-left corner).
- Navigate to Settings → Technical.
Step 2: Operational Data Parameters & Controls#
Ensure all mandatory parameters comply with enterprise operational standards:
- Authorized Operator: Action executed under assigned RBAC permissions (System Administrator, Certified Specialist).
- Relational Integrity: Linked to upstream master records, approval requests, or transactional ledgers.
- Statutory & Quality Controls: Verified against Ethiopian statutory regulations and corporate governance standards.
Step 3: Operational Execution & State Progression#
- State Progression Gate: Advance record from Draft through Audited to Confirmed / Certified.
- Integrated System Impact: Automatically updates real-time operational states and posts financial/inventory journal moves.
- Audit Verification: System registers tamper-evident audit records logging user ID, timestamp, and cryptographic transaction digests.
The four levels#
| Level | Who may read it |
|---|---|
| Public | Anyone, signed in or not. |
| Customers | Customers, and employees. |
| Partners | Partners, and employees. |
| Internal | Employees only. |
Customers and partners are portal users. You choose which by giving them the group Documentation / Customer or Documentation / Partner. A customer cannot read partner pages and a partner cannot read customer pages.
Sections narrow, never widen#
A page is as visible as the most restrictive of its own level and every section above it. A public page in an internal section is internal. The result is shown on the page as its effective visibility.
An unpublished section hides everything under it, whatever the pages say.
What a reader who may not read a page sees#
The page is simply not found: the same answer as for an address that does not exist, so the existence of an internal page is not revealed. Its title does not appear in the sidebar, the section list, search, the suggestions or the sitemap. Pages that are not public are never cached and are marked to stay out of search engines.
The same rule is used by the website, search, search-as-you-type, the sitemap and the API at /docs/api/v1, and the back office applies it again with record rules.
Drafts#
Only people who write or review documentation see drafts, and they are labelled. Reviewers and editors see every draft. An author sees the pages they wrote or own.
A good habit#
Set the visibility of a section when a whole area is restricted, and of a page only for an exception. Files can declare it too, with visibility: internal in the front matter.
4. Advanced Configuration Points#
- Automated Actions & Scheduled Tasks (Crons):
Documentation: Auto-rebuild search index(smarterp_docs.ir_cron_reindex): Runs on module upgrade to refresh full-text search indexes
- Custom Print Templates & Reports:
- SmartERP Technical Documentation Standards & Style Guide
- Documentation Coverage & Visual Asset Verification Matrix
- 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 |
|---|---|---|
Test Error: Broken link in documentation | Internal doc link refers to non-existent section or page slug. | Update link path to match valid section and page identifiers. |
Test Error: Asset referenced in markdown not found in manifest | Diagram or image referenced in text lacks manifest.json entry. | Register asset ID and file paths in static/img/manifest.json. |
Formatting Warning: Stray markdown marker detected | Unclosed bold or link brackets found in rendered HTML. | Ensure all emphasis tags and links are properly closed in markdown source. |