Notes Reference Public

FAQ and Troubleshooting

Answers to the most common setup, access, workflow, and support questions for the Notes module, with troubleshooting and support guidance.

Guide version: r2 Module version: 1.10.1 Updated: 2026-09-06 Estimated time: 4 min 15 views 0% helpful
Support

FAQ and Troubleshooting

Answers for the most common setup, access, workflow, and support questions for Notes.

Slug: noteVersion: 1.3.0Category: ProductivityReviewed: 2026-09-02

Frequently Asked Questions

Why can an admin see the module but a staff member cannot?

The module likely depends on both the module enable setting and role permissions. Confirm the module is enabled, then assign the relevant permission keys to the staff role and test with a non-admin account.

Why is a list empty even though records exist?

Check filters, deleted/archived status, tenant context, date range, ownership, and specific-member permissions. Some module lists intentionally hide records until a status, location, category, or assignment filter is selected.

What should we do before deleting or disabling records?

Confirm there is no active transaction, public page, report, job, or linked workflow depending on that record. Prefer deactivation or status changes when history must remain visible.

How do we know which screens belong to this module?

Use the Data and Screen Reference page. It lists controllers, routes, views, menu entries, and supporting files discovered from the module package.

When should this guide be updated?

Update it whenever routes, screens, permissions, public pages, APIs, jobs, seeders, reports, or the core workflow changes.

About the note categories

Why does one scribble open a drawing pad and another does not?

Scribbles drawn on the web keep their shapes, so opening one brings the pad back with everything still movable. A drawing that came from the mobile app, or a picture pasted straight into the text box, has no shapes behind it — only a finished image — so it opens as a plain note instead. That is deliberate: redrawing it through the pad would flatten and degrade the picture you already have.

My scribble saved without the drawing. Why?

Almost always the drawing pad column has not been added to this database yet. Ask your administrator to run the module migrations. A brand-new scribble with nothing drawn on the pad is also saved without a picture, on purpose — a blank sheet is not worth keeping.

Can I move a note into another category?

No. A note's category is fixed when it is created. Create the note from the tab you want it to live in, or recreate it there.

Why is a tab empty?

Each tab lists only your own notes of that category. A brand new Journal or Scribbles tab is empty until you (or the mobile app) create an entry of that kind.

Where did my old notes go?

Nowhere — every note that existed before categories arrived is an ordinary note and appears on the Notes tab.

Troubleshooting Checklist

  • Confirm the current tenant, user role, module toggle, and permission keys.
  • Reproduce the issue from the exact URL and record ID reported by the user.
  • Compare administrator behavior with a role-limited test user.
  • Review filters, deleted/archive flags, status, date ranges, and ownership fields.
  • Check recent module changes in README, CHANGELOG, migrations, and routes.

Glossary

Module slug
The stable key used by ERPat to enable, gate, and discover this module. For this module it is note.
Menu entry
The sidebar label a user clicks to reach the module workspace.
Permission key
A named access rule assigned to roles so staff can view, create, update, delete, report, or configure module records.
Route
A URL mapping from a browser path to a module controller action.
Seeder
An operator-run script that creates sample or starter data. Seeders are not the same as schema migrations.
Migration
A database schema change that prepares tables or columns required by the module.

Escalation Notes

  1. Capture the exact user, tenant, URL, record ID, date range, and action attempted.
  2. Check whether the same action works for an administrator and for a role-limited user.
  3. Review module routes, permissions, settings, migrations, jobs, and logs before changing data manually.
  4. Document the final cause in the module README, CHANGELOG, or this guide if it changes how users should operate the module.
Was this guide helpful?

Report a content problem