Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions for Tags and Correspondents #243

Open
goldi80 opened this issue Jan 27, 2025 · 0 comments
Open

Permissions for Tags and Correspondents #243

goldi80 opened this issue Jan 27, 2025 · 0 comments

Comments

@goldi80
Copy link

goldi80 commented Jan 27, 2025

Hi,

I've setup paperless with multiple users in private environment (household). I also created a dedicated API User for paperless-ai. In paperless frontend, I set permissions for newly created tags and correspondents to no owner and view and edit rights to my common group all users belong to. Furthermore, all documents are set to the same ownership/permissions by a workflow. With this setup, paperless-ai can process all documents either uploaded by any user or imported from consumption directory.

The problem now are the tags and correspondents created by paperless-ai. Unfortunately, the default ownership/permissions are only used, if objects are created via the web frontend, not if they are created via the API. Therefore, all newly created objects belong to the paperless-ai API User and the other users can't see them (they are displayed as private).

It would be great, if paperless-ai can read the ownership/permissions of the current document and uses them also for newly created tags and correspondents. This way, it would be guaranteed, that a user can access all tags and correspondents added to his documents.

Alternatively, paperless-ai can provide settings for ownership/permissions and uses them for all newly created objects.

Other thoughts and tricks are welcome. I just don't want to use one account for all members of our household. I think this will also be an interesting feature for small office groups.

Thanks for looking into it.
Stefan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant