InfoPath Dev

Im getting errors when general end users attempt to submit a form (infopath, web service deployed) to a restricted library. Hoping to leave the library forms are submitted to restricted to a few members only while general end users do not have access at all. Is this possible or do they have to have a minimum of read only? Users with full or Contribute have no errors submitting the form. If it is possible, can it be done without adding a bunch of code? Im not looking to write a bunch of how-to documents for when I win the lottery :)

Hello Imnverted,

For users to submit forms to a library they need to be able to have access to do so - just like any other library. That said, you have a couple options.  By default, users with "Contribute" permissions have Read, Write, Edit and Delete permissions. In the main site collection, (if you are the administrator) you can modify the permission levels of Sharepoint to include a permission level that is just Read and Add items. This way, users can submit the form to the library and not have full access to edit or delete any other items or even their own.

Another option is to have the form forwarded via workflow to another library with more restricted privileges and deleted from the original library upon submission. So the process would be that the form is submitted to the library. A SPD workflow is automatically started upon form submission that copies that file to another library and then a workflow action on the second library deletes the form from the first library. Or if you are a programmer, you could develop a workflow in .NET that changes the permissions upon submission. Does this help? (If it does, please send those winning lottery numbers!)

 Janice

You can also use SSO to submit in secure library. You need to configure SSO in your data connection file. This way you can restrict write right to only one user.

Sorry to bring back an old thread but it's relevant to what I am looking for. Can someone elaborate on mayurnagda or direct me to an appropriate document that explains this type of setup. We are already using Single Sign on for Sharepoint but I am not sure how you specify this with Qdabra.

I am assuming that mayurnagda is talking about using one account with write only for form library submission. Rather than opening the form library to contribute access for moving form to form.... thanks

I think I found a solution to this problem and I will post it here for discussion.  The solution that mayurnagda seems more eloquent if it's a solution.

Purpose, allow any user to submit to a more secured form library using DBXL:

1.  Create a new Permission Access Level (DBXLSystemuse)

Give acces to, Add Items, Edit Items, Delete Items, View Items and Approve Items in List Permissions.  These seem to be the minimal set necessary for DBXL to perform the auto delete and additions of your forms under the users' account.

If you don't give the user, "View Application Pages" right, they won't be able to open the page to that library.  They will get an Access Denied, eventhough they have rights to add, edit and deletes to the list.

2. Create a new Group with users list using the new Permission Access Level(DBXLUsers)

3. Break inheritance for the Form Library you need secured, add DBXLUsers to this list as well as your administrator's group.

In Addition, if you are using form workflow with a configuration file as a Sharepoint list as suggested by Qdabra webinar; the mininal permission configuration is:

Do the same as above, but give acces as follow: View Items, View Versions, Create Alerts and View Applications

The above access rights will allow the form to read the configuration file and wont allow the user to edit/delete.

 The result will allow a more secure form list while allowing DBXL to perform its automatic form additions and deletions.  The user won't beable to see the link to the secure form and if they go to it directly will receive an access denied error page.

 

If anyone has a better idea to accomplish that, please chime in.