Security & control

Application controls built into the way cooperative work moves through Fortunato.ph.

Fortunato.ph uses configured authorization, transaction-state checks, audit records, and optional approval workflows across supported cooperative operations.

CONNECTED CAPABILITY

Access follows responsibility.

Different users can be given access according to the work they actually perform.

Roles & permissions

Configured roles and permissions control access across protected areas and supported actions.

Module-aware access

Optional modules can be enabled for the cooperative while permissions still determine who may use them.

Transaction state

Supported operations validate both the user’s permission and the transaction’s current lifecycle state.

Administrative controls

Configuration and administrative areas use separate, permission-restricted access.

CONNECTED CAPABILITY

Approval and accountability are shared platform concerns.

Where enabled and configured for a supported transaction type, Fortunato.ph uses its shared Workflow & Approvals engine.

Workflow & Approvals

Configured workflows can control review, return, rejection, and final authorization across applicable modules.

Authoritative active workflows

For supported transaction types, an active workflow instance prevents the corresponding direct action from bypassing it.

Audit trail

Important platform and transaction activity is recorded with user, action, entity, description, and timestamp details for operational traceability.

Historical preservation

Changing optional module availability does not itself delete records already created in that module.

QUESTIONS & ANSWERS

What cooperatives usually ask.

Practical answers about this part of Fortunato.ph and how it fits the wider platform.

Does Fortunato.ph use role-based access?

Fortunato.ph uses configured roles and permissions across protected areas and supported actions.

How are approvals handled?

Where enabled and configured for a supported transaction type, transactions can use Fortunato.ph’s shared Workflow & Approvals engine.

Does disabling a module delete its historical data?

No. Changing optional module availability does not itself delete records already created in that module.

What does this security page cover?

This page describes application-level controls. Hosting, backups, monitoring, disaster recovery, data residency, and independent assurance depend on the applicable deployment and operating arrangements.