You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if one could define "drop email"-addresses for folders individually, i.e. if a business organizes its documents per project or client, it can send directly to that particular folder.
Right now the emails get stored by sender and date, but this sort logic might not be the most convenient for all use cases, or might be more convenient for users, if they can define the target folder. This way the mails would remain in its context.
All documents for a project, regardless which employee has sent the email, will go to the relevant project folder, not split across sender folders, even though the documents belong to the same project.
Still, some kind of differentiation would be needed, such as timestamp, in order to avoid naming conflicts though of course.
The text was updated successfully, but these errors were encountered:
Would be nice if one could define "drop email"-addresses for folders individually, i.e. if a business organizes its documents per project or client, it can send directly to that particular folder.
Right now the emails get stored by sender and date, but this sort logic might not be the most convenient for all use cases, or might be more convenient for users, if they can define the target folder. This way the mails would remain in its context.
They can use one single email account with certain addition using + such as the project or customer id, so for example:
[email protected]
[email protected]
[email protected]
etc.
All documents for a project, regardless which employee has sent the email, will go to the relevant project folder, not split across sender folders, even though the documents belong to the same project.
Still, some kind of differentiation would be needed, such as timestamp, in order to avoid naming conflicts though of course.
The text was updated successfully, but these errors were encountered: