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
Currently blindsend supports the Send file and Request file workflows. However, the design of the homepage only allows to have a permanet link to the entry point to the Send file workflow. The user can only switch to the Request file workflow if they click on the "Request" tab/button.
What should be done
There should be a permanent link leadning directly to to the entry point of the "Request file" workflow. Giving that link to the user should lead the user directly to the same interface as if the user clicked on the "Request" tab/button.
Also when the user clicks on the "Request" tab/button, the URL of this permanent link should appear in the address bar, allowing the user to discover the permanent link (and share it).
Why
An organization using blindsend to collect confidential files (e.g. a lawfirm) might want to write a "how to" document giving their members instructions on how to use blindsend, instead of e-mail, to collect files from their clients. Currently this "How to" is made complex as one needs to explain how to click on the "Request" tab/button.
Giving a direct link to this workflow's entry point would make things easier.
The text was updated successfully, but these errors were encountered:
Currently blindsend supports the Send file and Request file workflows. However, the design of the homepage only allows to have a permanet link to the entry point to the Send file workflow. The user can only switch to the Request file workflow if they click on the "Request" tab/button.
What should be done
There should be a permanent link leadning directly to to the entry point of the "Request file" workflow. Giving that link to the user should lead the user directly to the same interface as if the user clicked on the "Request" tab/button.
Also when the user clicks on the "Request" tab/button, the URL of this permanent link should appear in the address bar, allowing the user to discover the permanent link (and share it).
Why
An organization using blindsend to collect confidential files (e.g. a lawfirm) might want to write a "how to" document giving their members instructions on how to use blindsend, instead of e-mail, to collect files from their clients. Currently this "How to" is made complex as one needs to explain how to click on the "Request" tab/button.
Giving a direct link to this workflow's entry point would make things easier.
The text was updated successfully, but these errors were encountered: