We would like to provide links in emails to files stored by SuperContainer, and we like the way that "Raw Data" works.

However, is there a way to conceal the SuperContainer user name and password, but still provide access to the file? Or somehow automate the system to copy the file to a download location?

Don't know enough about your business process but you could build a download queue in filemaker and send the user a link to record in the queue (a web publishing link) or if they have FM10 even a snapshot link where they can then click a button and have the file downloaded.

How do I build a download queue in FM? Is there any documentation for this?

Hi Steve - one approach you could take is using a randomized key as part of your SuperContainer URL, instead of a username/password. By assigning a different randomized key to each SuperContainer URL, you can effectively control who can access each resource.

You can read more about this technique on our FAQ wiki:

http://wo.360works.com/cgi-bin/support/productsupport.cgi/SuperContainer#SuperContainer48

Jesse -- this looks like a great approach (I can't believe I didn't notice this suggestion before).

What would you suggest we do about all the clients whose documents aren't already stored in randomized folders?

Also, would you store the randomized folder name, or base it on a hard-to-guess calculation?

You will need to store the random key in a field in a way that does not change, such as an auto-enter calc with the checkbox to not overwrite existing values. Then you can set up FileMaker access privileges to control, on a record-by-record basis if necessary, who has access to that field, and by extension, that resource in SuperContainer.

You can use SCMove function in the optional companion plugin to loop through all existing records and reassign their URL.