Wednesday, December 4, 2024
1 change · 18.0
Security fixes and vulnerability patches
This fixes cases where documents linked to or moved out of a project could keep the wrong internal access level after project visibility changed. Businesses get more reliable document privacy so access matches the intended project settings.
Original PR description
Two flows are fixed and tested in this PR: A/ 1. Create a document outside a project's folder 2. Link the document to a project/task without moving it 3. The document's access_internal value is not synced with the privacy visibility as it would have if we had moved it inside the project's folder instead B/ 1. Create a document in a project's folder with privacy visibility 'employees' 2. Move the document outside the project's folder 3. Update the privacy_visibility to 'followers' 4. The document is still accessible to all internal users while it shouldn't Note: _add_missing_default_values was an unused remnant of a distant idea Task-4242299