This is another post in our current series, which looks at the features included in the Administration Center for Office 365 E3 Sharepoint Online.
Office 365 E3 Plan SharePoint Online Administrators can configure InfoPath Forms Services through the Administration Center. It is important to note that ” . . . configuration settings [effected through the Administration Center] apply only to user form templates. User form templates are form templates that are not deployed by an administrator” (quoted from an article, Configure InfoPath Forms Services from the Microsoft® Office web site).
Through a series of mouse clicks, administrators can configure InfoPath Forms Services to support governance policy as well as data security best practices. At the highest level, administrators can either choose to enable InfoPath Forms Services, or not. If enabled, users will have the ability to build form templates for browser processing. Browser processing does present data security risk. Therefore, providing administrators with an option from this screen to remove user rights to build InfoPath Forms for browser processing makes sense.
Administrator control over the feature is granular. Administrators can permit users to build InfoPath Forms for browser processing, but choose not to permit rendering of these forms. This type of setting gives administrators an opportunity to provide Line of Business (LOB) users with a sandbox where they can safely learn to build InfoPath Forms for browser processing. Once these users have demonstrated that they have correctly built the forms, then administrators can enable SharePoint Online Server to render the forms for browser processing.
Search tools that index browser forms can present organizations with a risk of data loss by exposing processes that should be invisible to unauthorized users. The Administration Center configuration options for the InfoPath Forms Services also provides administrators with a no-code method, through the browser, to properly configure the robots.txt file for the server to exclude specific crawlers, as appropriate.
In the next post to this blog we will look at the Term Store configuration options included in the Administration Center.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved