Skip to content

Organizations, permissions, and a move to PostgreSQL

Studio gains organizations with centralized CASL permissions and fail-closed authorization, moves its database from MongoDB to PostgreSQL, and links stories and bugs both ways.

Updated View as Markdown
For humans

The largest structural change since Studio launched, and — apart from the new organization surfaces — one you should barely notice.

Organizations

Projects now live inside an organization. Membership, invitations, and project access are managed at the organization level, and an organization admin can grant or revoke a member’s access to individual projects from one place.

Permissions run through a single centralized CASL policy rather than checks scattered across the codebase, and request authorization is fail-closed: an action with no rule permitting it is denied rather than allowed. Guest access to a project, sprint permissions in the UI, and project-wide roster mentions all read from that same policy.

PostgreSQL

Studio’s database moved from MongoDB to PostgreSQL, with Prisma models, migrations that run in production, and UUID identifiers throughout. Tokens carrying a pre-migration Mongo ObjectId are rejected rather than half-resolved.

Stories and bugs, linked both ways

A bug can be linked to one or more user stories, and a story shows the bugs linked to it — searchable from either side, unlinked individually, with the links written atomically so concurrent edits resolve cleanly. Bugs also gained an Estimate field with the same parsing and formatting as user stories.

Also in this release

  • Meetings record which kind of input they came from, including recordings made by the meeting extension.
  • Figma and several legacy pages were removed, and the sprint task status SSE endpoint was retired.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close