[GH-ISSUE #618] Missing features for folders #486

New issue

Open

opened 2026-02-25 21:32:01 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:32:01 +03:00

Owner

Originally created by @karabomaboka on GitHub (Jun 14, 2024).
Original GitHub issue: https://github.com/ciur/papermerge/issues/618

Originally assigned to: @ciur on GitHub.

Description
I'm running Papermerge version 3.2 and I'm unable to see the permission features for folders. I've logged in as an admin, but the folder settings only show basic options like OCR, tags and delete. I'm expecting to see permission settings like "Edit permissions" or "Access control" to manage user access to folders.
Am I missing something? Is this a known issue or a configuration problem?

Expected behavior:
As an admin, I should be able to see and manage permission features for folders to control user access.
Actual behavior:
The permission features are not visible in the folder settings.

@karabomaboka
Info:
-Papermerge version 3.2

Originally created by @karabomaboka on GitHub (Jun 14, 2024). Original GitHub issue: https://github.com/ciur/papermerge/issues/618 Originally assigned to: @ciur on GitHub. **Description** I'm running Papermerge version 3.2 and I'm unable to see the permission features for folders. I've logged in as an admin, but the folder settings only show basic options like OCR, tags and delete. I'm expecting to see permission settings like "Edit permissions" or "Access control" to manage user access to folders. Am I missing something? Is this a known issue or a configuration problem? Expected behavior: As an admin, I should be able to see and manage permission features for folders to control user access. Actual behavior: The permission features are not visible in the folder settings. @karabomaboka **Info:** -Papermerge version 3.2

kerem added the

feature request

3.x

labels

2026-02-25 21:32:01 +03:00

kerem commented

2026-02-25 21:32:01 +03:00

Author

Owner

@ciur commented on GitHub (Jun 15, 2024):

No, you are not confusing anything.
The feature you are asking was part of 2.0, but then temporary removed. It is not there in 3.2, but will be back very soon (in 3.3, 3.4 or 3.5) which will be this year.

@ciur commented on GitHub (Jun 15, 2024): No, you are not confusing anything. The feature you are asking was part of 2.0, but then temporary removed. It is not there in 3.2, but will be back very soon (in 3.3, 3.4 or 3.5) which will be this year.