I had an issue with the resume later in that the user was not able to bookmark the point in which they saved within a survey. After putting in a bug report, I was advised that the clean URL was done for security and other reasons. The following is my hack to allow folks to have a URL that they can return to when they save.

I agree all of the save/resume features in LS are pretty confusing. My preference for allowing save/resume is token persistence, but if you hit "resume later" it saves but leaves you right at the same page, which is confusing. They also used to send an email every time somebody hit save, which got a little tiresome. Then they got rid of the email and people couldn't find the original invitation with the link.

My solution was to put a login "wrapper" script around the survey. They pass through the script to reach the survey so the actual survey url is never exposed, and when they press resume, I trap that and prompt them to create a username and password in my login system. After that, anybody who comes in with the original invitation URL can only resume the survey with username and password. And the participant doesn't need the "long" invitation URL because he can just go to the research home page (eg, mysurveys.com or whatever) and log in there and see his survey.

I see thanks. So you are using tokens. Personally I like the clean URL, because as soon as some data is in the survey there are privacy/confidentiality issues and I don't want that URL to be left around in bookmarks or accidentally forwarded to other people etc. But different strokes...

Yes, we do use tokens (but the client never sees these) - we have hijacked the entire logon process and removed email check, etc. and came up with our own that is based on a medical record number and another value for authentication. This allows our survey takers to take the survey multiple times having different tokens for history.