← Back to all sparks
P

Passbolt

COLLAB
Velocity5.0

Open-source password manager for teams

Passbolt keeps rebuilding the sharing dialog because that is where its access model leaks.

password-manageraccess-controlsharingsession-managementautofillsecurity-fixes
Current state
Three consecutive releases have gone into permission transparency. 5.14 introduced confirmation prompts before editing shared resources and surfaced group members in the access list; 5.14.3 corrected two behaviours it got wrong; 5.15 adds badges showing whether a permission is added, modified or deleted, and lets a deletion be rolled back before confirmation. 5.15 also moves sessions into the database with a PurgeSessions command and a healthcheck reporting the active provider, and closes three externally reported bypasses around personal-folder sharing and V5 tag promotion.
Where it's heading
The product is treating accidental over-sharing as its primary risk, and the fix is repeated iteration on the moment of change rather than a new permission model. The company has said this is staged work — folder moves and richer preview dialogs are named as future extensions. In parallel the platform side is maturing for larger installs: database-backed sessions, edition switching in-app since 5.13, healthcheck coverage, SCIM administrator-deletion guards. Autofill has just started its own multi-release arc, with 5.15 explicitly the first step.
Prediction
The next release should extend confirmation prompts to folder move operations, and the notes flag that the SSO egress guard will default to on. Autofill form classification is the other named thread, with a technical write-up promised after the following release.

Recent moves

  1. 26d ago

    5.15 adds database sessions and closes shared-tag permission bypasses

    Continues the permission-transparency arc with add/modify/delete badges and rollback of deleted permissions before confirmation, and starts the autofill form-detection series. Underneath it moves sessions to database storage with pruning and healthcheck reporting, rejects JWTs for disabled users, and fixes three reported bypasses that let non-owners promote or unlink V5 tags and share personal folders.

    View source ↗
  2. 1mo ago

    5.14.3 limits the permission dialog to actual secret changes

    Corrects the 5.14 dialog firing on metadata-only edits such as renaming, and makes it read-only when a user creates a resource in a shared folder they do not own so inherited permissions cannot be overridden. A quick fix to a feature that had over-reached in its first form.

    View source ↗
  3. 1mo ago

    5.14 adds confirmation prompts before shared-resource edits

    Introduces the explicit confirmation dialog that the following two releases spend their time refining, and shows group members inline so the real reach of a share is visible. Also reranks browser-extension suggestions by URL relevance so exact matches surface first.

    View source ↗
  4. 3mo ago

    5.13 adds in-app switching between Community and Pro

    Builds on the 5.12 codebase unification so administrators can move between editions from settings rather than running manual migrations. Also adds cache availability to the healthcheck endpoint and starts paginating resource fetching for large credential sets.

    View source ↗
  5. 4mo ago

    5.12 makes the Safari extension generally available

    Ends the Safari open beta and puts it level with Chrome, Firefox and Edge, and adds a dedicated PIN code resource type with its own form, validation and numeric generation. The codebase unification landed here is what made 5.13's edition switching possible.

    View source ↗