Roles & permissions
Use Fortunato’s authorization model to control access to pages, modules, and permitted actions.
Security & control
Controls built into the way cooperative work moves through Fortunato.
Fortunato combines authorization, audit history, transaction state, and shared approval workflows so operational controls are part of the platform—not an afterthought bolted onto individual modules.
CONNECTED CAPABILITY
Access follows responsibility.
Different users can be given access according to the work they actually perform.
Module-aware access
Optional modules can be enabled for the cooperative while permissions still determine who may use them.
Transaction state
Actions can be limited by both permission and the transaction’s current lifecycle state.
Administrative controls
Configuration and administrative areas remain separated from ordinary operational work.
CONNECTED CAPABILITY
Approval and accountability are shared platform concerns.
Where review or authorization is required, Fortunato uses common infrastructure rather than inconsistent module-specific shortcuts.
Workflow & Approvals
Configured workflows can control review, return, rejection, and final authorization across applicable modules.
Authoritative active workflows
An active workflow instance remains authoritative for its transaction and prevents native actions from bypassing it.
Audit trail
Important platform and transaction activity is recorded for operational traceability.
Historical preservation
Disabling an optional module does not mean deleting the historical records already created under it.
QUESTIONS & ANSWERS
What cooperatives usually ask.
Practical answers about this part of Fortunato and how it fits the wider platform.
Does Fortunato use role-based access?
Fortunato uses roles and permissions to control what users can access and which actions they may perform.
How are approvals handled?
Transactions that require review or authorization can integrate with Fortunato’s shared Workflow & Approvals engine where applicable.
Does disabling a module delete its historical data?
No. Module availability and historical data are treated separately so existing records are preserved.