Roles & permissions
Configured roles and permissions control access across protected areas and supported actions.
Fortunato.ph uses configured authorization, transaction-state checks, audit records, and optional approval workflows across supported cooperative operations.
Different users can be given access according to the work they actually perform.
Configured roles and permissions control access across protected areas and supported actions.
Optional modules can be enabled for the cooperative while permissions still determine who may use them.
Supported operations validate both the user’s permission and the transaction’s current lifecycle state.
Configuration and administrative areas use separate, permission-restricted access.
Where enabled and configured for a supported transaction type, Fortunato.ph uses its shared Workflow & Approvals engine.
Configured workflows can control review, return, rejection, and final authorization across applicable modules.
For supported transaction types, an active workflow instance prevents the corresponding direct action from bypassing it.
Important platform and transaction activity is recorded with user, action, entity, description, and timestamp details for operational traceability.
Changing optional module availability does not itself delete records already created in that module.
Practical answers about this part of Fortunato.ph and how it fits the wider platform.
Fortunato.ph uses configured roles and permissions across protected areas and supported actions.
Where enabled and configured for a supported transaction type, transactions can use Fortunato.ph’s shared Workflow & Approvals engine.
No. Changing optional module availability does not itself delete records already created in that module.
This page describes application-level controls. Hosting, backups, monitoring, disaster recovery, data residency, and independent assurance depend on the applicable deployment and operating arrangements.