Submissions often contain personal or sensitive information. Use this checklist to make sure only the right people can see and change them.
Checklist
|
Check |
Why |
Where |
|---|---|---|
|
Serve GlobalForms over HTTPS. |
Protects submissions and sign-ins in transit. Never run production workloads without HTTPS. |
|
|
Review "All" permissions on every form. |
Read All, Update All and Delete All expose every submission of the form. By default no role has them; grant them only to small, specific roles. |
|
|
Give Anonymous only Create Own on public forms. |
Lets the public submit without being able to read other submissions. |
|
|
Keep the Authenticated role narrow. |
Every signed-in user, including self-service and synchronized users, has it. |
|
|
Restrict file uploads. |
Allow only the file types you need, and require sign-in where possible. |
|
|
Store service passwords on the server. |
Keeps PDF account passwords out of form definitions and exports. |
|
|
Decide how deleted data is handled. |
By default, deleted submissions stay in the database. |
|
|
Protect the server and database. |
Limit access to the install folder, |
Submissions in GlobalCapture
Form permissions apply in GlobalForms. When a submission is in a GlobalCapture workflow, GlobalCapture's security also applies. For example, validation actions on a submission are shown only to users secured to that workflow step.
Forms used outside your network
If people outside your organization use your forms, also review Ports and External Access and Security Headers.