Skip to content

Case studyORGAN.SYS2026

Organ, collaborative project management

Modular project management platform with a web client, a native Android app and real-time updates.

Demo of the Organ web client on a demo account, subtitled in French, English and Chinese.Muted demo video recorded on a demo account: personal data is pixelated. The subtitles are a narration I wrote (French, English, Chinese); pick the language in the player controls.

[01]Context and principle

Organ is a project management platform built by a team of three within Voxel Studio. Each project is divided into "organs": autonomous sub-spaces with their own members, roles and permissions. It includes a Kanban board, a list view, statistics, an audit log and a built-in AI assistant.

Give each collaborator only what they need: a member only reaches the organs where they hold a role. A role can be copied from one organ to another, then its permissions are adjusted organ by organ.

[02]Architecture

Symfony 8 backend, Angular front end, native Android app in Kotlin (Compose).

Polyglot persistence
MySQL for relational data, MongoDB for the audit log. Depending on configuration, attachments are stored in GridFS or sent directly to the user's own Drive.
Real time
Updates pushed through Server-Sent Events (Mercure) to web and Android.
Fine-grained permissions
Hybrid RBAC: global roles plus local permissions for each organ.

Other technical and functional choices

ChoiceEffect
Google sign-in (OAuth 2.0)On the web and on Android.
Built-in AI assistant (commands /create, /edit, /role, /ask)A switch lets the user authorize it to act on their behalf.
"Bring Your Own Storage"Depending on configuration, files are stored in GridFS or go straight to the user's own Google Drive; in that case Organ only keeps the metadata.
Project and global trash binsRestore or delete permanently.
Revocable active sessions; account deletionImmediate deactivation, then permanent erasure after 30 days without signing in again (GDPR).

[03]Kanban and tasks

Columns by status, priorities, tags and due dates; task sheet with its activity history.

[04]Roles and permissions

Grouped permissions, adjusted organ by organ; a role can be copied from one organ to another.

[05]Statistics and audit

30-day statistics, activity by organ and an audit log filtered by action type and period.

[06]AI assistant

Commands /create, /edit, /role, /ask; a switch lets the user authorize the assistant to act on their behalf.

[07]Results and limits

Results

My share of the project is given in the fact sheet at the top of the page: figures taken from the repository, verifiable on the GitHub contributors graph.

Limits

  • The screenshots use fictional demo data; the video was recorded on a demo account with personal data pixelated.
  • Commit and code shares describe how the work is split in the repository, not anyone's quality. The code share excludes lockfiles, generated files, migrations, JSON/assets and documentation.
// Next projectPrivy, end-to-end encrypted messagingFORMAT: POST-MORTEM REPORT

Let's talk

A question about this work, or want to see more? Write to me.

Contact me