[Feature Request] multiple consume folders + set default owner per folder

[thiswillbeyourgithub]

Description

Hi,

I think I understood that when I upload a document using the GUI or the phone app, the document automatically has my account assigned as owner, but if a document is added via the consume folder then no owner is set.

1. Is it possible to specify a default owner for files coming from the consume folder?
2. Is it possible to have several consume folders ?
3. Is it possible to implement a workflow trigger for the consume folder? That would solve 1. because I could just say "if it comes from this folder then set owner to XYZ"

Thanks

Other

No response

[github-Jan]

You can use a consume folder with the usersnames
eg:
/usr/share/consume/alice
/usr/share/consume/bob
/usr/share/consume/eve

in docker-compose.env i have set following for "nicer storage" -> each user has "his" documents in subfolder. the recursive consume is needed for the workflows (see below)

PAPERLESS_FILENAME_FORMAT={owner_username}/{created_year}/{correspondent}/{document_type}/{title}
PAPERLESS_CONSUMER_RECURSIVE=true

As workflow:
have one per user
Workflow 1 "Alice"
Consumption started:
Filter path
*alice/*

Action -> set owner Alice

Workflow 2 "Bob"
Consumption started:
Filter path
*bob/*

Action -> set owner Bob
Workflow 3 "Eve"
Consumption started:
Filter path
*eve/*

Action -> set owner Eve

Now a document in /usr/share/consume/alice will be assigend to User Alice
Now a document in /usr/share/consume/eve will be assigend to User Eve

(edited for typos and escaped "*")

[stumpylog]

This is the correct way of assigning owners via the consume folder

[thiswillbeyourgithub]

Thank you both, I had not thought of that. But doesn't that delete the subfolder once its done? If yes I'm guessing that by changing the subfolders UNIX permission I can forbid that. Can you confirm that's the supposed way?

[github-Jan]

No. It will remove the files from the folders, but the folders itself are not consumed.
-> no need for special UNIX Permissions, as long as each user can place the files in the resp. folder AND paperless has read and write access there (to remove the files)

[thiswillbeyourgithub]

Thank you

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.