Wish List: Email link to file

This is a major feature but common in similar products. 

It would be useful to be able to email a link to a document so that recipient does not need to login to receive the file.

Thanks, Simon

This is in our to-do list along with send files as email attachment feature.

What is the time frame on this?

This feature may be included in a month or two.

I have a similar feature request:
It would be nice to be able to send out email notifications when a specific user-action has taken place. i.e. deleting a file or uploading files to a specific folder which has some kind of "monitoring" status.

Any new updates on the directlink to a file option?

Has it been included yet?

Sorry Emiel,
As of current version 3.5, this feature is not added yet.

Is it part of 3.6? 
I did not found it in the demo.

The ability to copy an URL for pasting in documents or to send an URL within e-mails is essential. I need a file publishing server with stable URL's which can be referenced in other systems and in documents. Thought FileVista could be a smart choice.

I agree - we really need a way to link directly to documents. That is an essential feature we need when we are posting news stories or sending emails. Link to this file and Link to this folder are really needed in this sytem!

Up.

Any updates on this? Since August we had several month.

an update when this will be available would be nice after these many months.

Up

it's now in 4.0 as direct link implemented.

I tested it on your demo server. It has some big functionality. It's a good feature.

It has some room for improvement. Most missing thing is, in the generated E-Mail, the original filename and filepath inside the repository is not seen. So only the alias name or the generated UUID is shown.

Another disadvantage is all sent files are shown in the URL as they are in same folder ...filevist/link/* . If you like to send files with the same filename out of different folders, then you cannot use the origin filename.

Hi,
I think the path (location of the file) is irrelevant for the direct link feature. Actually it's better not to display it in the URL for security reasons. Another reason is that we wanted to keep the URL as short as possible. Users would not want to see broken, long and ugly links in their email clients.

You should think the generated URL as a ticket to a protected file not a path to the actual location. For your purpose, there is the option to use a "custom name" instead of a GUID in the URL. You can enter the original file name or a more descriptive name (eg. a file name including folder names with dashes) in this field.

If you don't want to struggle with same filename issues, you should just keep using the default GUID names, they are for that purpose.

Note that in the next versions, giving direct links to folders will be also possible, maybe this will be useful to you.

Hello Cem,

thanky you for your answer.

I think to use this UUID as name in the Link or to use an self defined ALIAS could be ok. Maybe the way the alias is created could be enhanced, so you can include parts of the path without typing them in, or a pre-fix, per-user defined (e.g. projectname).

What could be an option is, to have the Full path (not the URL) as description in the E-Mail text, above the URL.

Another option, selectable by the user, could be "create and send fullpath URL" (I know you don't like this ugly URL's)

My usecase is a big project archive, where for each project the same directory tree exists. So most folders and files are the same names. Only the toplevel directories have different names. With your current implementation is more or less not possible to send the links, or reference them in documents, except you use the UUID. But then you don't know from which project (toplevel directory name) the file is comming.