I needed to meet a security requirement for an InfoPath form today. In this business situation, a relatively small number of individuals are allowed to create a new InfoPath form and a much wider audience are allowed to edit it. (Esta é a nova contratación en boarding forma utilizada pola área de recursos humanos, que lanza un fluxo de traballo).

Para alcanzar este obxectivo, Eu creei creou dous novos niveis de permiso ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, actualizar" user and a separate "update only" usuario. The mechanics all worked, but it turned out to be a little more involving than I expected. (If you feel a little shaky on SharePoint permissions, check out this blog post). The required security configuration for the permission level was not the obvious set of granular permissions. To create an update-only permission level for an InfoPath form, Eu fixen o seguinte:

1. Create a new permission level.
2. Clear away all options.
3. Selected only the following from "List permissions":

• Edit Items
• View Items
• View Application Pages

Selecting these options allows a user to update a form, but not create it.

The trick was to enable the "View Application Pages". There isn’t any verbage on the permission level that indicates that’s required for update-only InfoPath forms, but turns out it is.

Create-and-Update was even stranger. I followed the same steps, 1 through 3 arriba. I had to specifically add a "Site Permission" option: "Use client integration features". De novo, the description there does not make it seem like it ought to be required for an InfoPath form, but there it is.

</final>