DevFloHQ
Menu

Security overview

Practical safeguards for an invitation-only platform.

DevFloHQ is being developed carefully, with organizational isolation, limited access, and responsible data use as core requirements.

Organization isolation

Each authorized user is linked to one organization. Database row-level security restricts ordinary sessions to records belonging to that organization.

Invitation-only access

Accounts are provisioned directly. There is currently no public signup path, and access should be removed when a participant no longer needs it.

Least necessary data

Pilots should begin with limited information and avoid sensitive data. The safest useful dataset is preferred over copying an organization’s entire history.

Human review

AI-assisted outputs and automated workflows require human review. Relationship decisions, approvals, and organizational judgment remain with people.

CCSC model and staff roles

The entire CCSC workspace is a running model. Programs practice records are temporary. System Admin, Programs Staff, Development Staff, and Front Desk views describe the intended access model; preview role selectors do not enforce live permissions. Private assistance must be protected in the database, client profiles, searches, reports, and exports before operational use.

Payments and migration readiness

The CCSC model does not collect or store card details, charge cards, or email receipts. Before moving real donor or client records, validate access controls, secure storage, audit history, backup restoration, reconciliation, and support. A provider integration and confirmation flow need separate implementation.