Approval is how a company puts a name to a decision. The rules are simple and uniform:
- Approval is a permission, per kind of document. Your role may let you approve sales orders but not payments; approve purchase orders but post nothing. If you cannot approve a document, its Approve action simply is not on the page (see 1.12). The person who approves need not be the person who drafted — and in many companies must not be.
- Approvals are recorded. Who approved, and when, is part of the document's permanent record, visible on its page and in its Activity trail.
Notifications arrive through the bell at the top of every screen; a badge counts what you have not yet read, and the list refreshes on its own as you work. The bell is where BlossomERP reaches you: when a colleague mentions you in a note on a record, when a follow-up you are part of comes due, and — where a workflow hands work from one person to the next — when something lands in your court, such as work awaiting your approval or posting. Clicking a notification takes you to the record or document it concerns, not to a dead-end message.
Work that is waiting for you is also always findable in place: every document list can be filtered by status, so "drafts awaiting approval" and "approved, awaiting posting" are one filter away in the module where the work lives — and the module cockpits of Chapter 2 are built to surface exactly those queues.