Security and trust
Trust starts with visible controls.
Rosella is built for research teams that need participant workflows to be deliberate, reviewable, and governed without making day-to-day coordination harder.
Controls
Security is part of the workflow, not a separate checklist.
Rosella's trust model is grounded in visible access, explicit project state, scoped integrations, and participant journeys that staff can review before and after they change.
Role-based access
Workspace, team, and project membership give teams a practical way to separate broad administration from project-specific coordination.
Authentication controls
Staff can use password or Google sign-in with TOTP protection, participants can use email one-time codes or Google, and Organization workspaces can connect a tenant-bound OIDC identity provider.
Audit-ready operations
Rosella models staff decisions, approvals, version changes, participant events, messaging, and completion history as part of the operational record.
Integration scopes
External connections are scoped at workspace, team, or project level where supported, with fallback behavior made explicit to staff.
Project versioning
Draft, review, publish, and migration flows help teams change study protocols deliberately instead of silently changing live participant journeys.
Least surprise for participants
Participant-facing flows are designed to show registration state, requirements, documents, consent, booking steps, and follow-up work clearly.
Governance
Make sensitive participant operations easier to inspect.
The safest workflow is often the one your team can actually see. Rosella keeps operational state close to the decisions staff need to make.
- Workspace and project boundariesTeams can separate workspace administration from the staff who need access to a particular study.
- Reviewable change pathsProtocol changes can move through drafts, approval, publication, and participant migration rather than being improvised live.
- Participant data in contextCoordinators can review status, screening, activities, messages, sessions, and notes together before taking action.
Choose the governance level your research program needs.
Plans scale from solo researchers to organizations that need enterprise OIDC SSO, audit logs, auth events, and session management.