Xerox SmartSend Support & Software Installation Guide

Page of 198
9-8
SMARTsend Security
PaperWare Forms
Professional Edition feature
A cover sheet is a type of PaperWare form. This policy determines whether a PaperWare cover sheet is 
considered a valid form of user authentication. There are two options for the PaperWare Form Security 
Policy, Allow authentication with PaperWare forms only, and Require PaperWare form and login at the 
device for authentication. 
Allow authentication with PaperWare forms only
This is the default PaperWare Form Security Policy. Each PaperWare cover sheet has an owner specified in 
the top left corner of the cover sheet header. The owner is the SMARTsend user who created the PaperWare 
cover sheet by publishing the workflow. Using this option, the cover sheet owner’s credentials will be used 
to authenticate the scan job submitter. With this policy set, private workflows can be published as PaperWare 
cover sheets and the owner specified in the cover sheet will be used to authenticate the scan job submitter. 
This allows for the use of private templates in environments that do not have Xerox Multifunction Devices 
with authentication enabled. 
Note that if a user scans from a Xerox Multifunction Device that has authentication enabled, they will still 
be prompted to authenticate at the device. The credentials entered at the device will be used in place of the 
credentials on the cover sheet.   
Require PaperWare form and login at the device for authentication
This policy option does not allow the owner specified on the PaperWare cover sheet to be used to 
authenticate the scan job submitter. This is the highest PaperWare Form Security Policy setting. If this policy 
option is selected, private workflows published as PaperWare cover sheets will require authentication at a 
Xerox Multifunction Device in order to identify the scan job submitter. Cover sheets created from private 
workflows will not work when scanning over Internet Fax, because the user will not be given the 
opportunity to authenticate. Refer to the Security Policy Interactions section below for details.