ITS Helpdesk

Phone: 810.762.3123 opt. 1 - Email:

FormAssembly - General Information

Last Updated: Jan 17, 2017 09:17PM EST

FormAssembly is a web form creation and processing service. Web forms provide the university with an easy way to collect information, without all the messy paperwork. FormAssembly also makes it easy for users to generate forms specific to their needs.

Intended Audience

This Quicknote is intended for current faculty and staff who would like to know more about using FormAssembly.


To follow this Quicknote you will need to have access to FormAssembly. To get access to FormAssembly, please keep reading.

What are the best uses for FormAssembly?

Is your department looking for feedback on a new program or policy? Do you need students, faculty, and/or staff to RSVP for an upcoming event, but don’t want the hassle of dealing with paper RSVPs? All of these are possible using forms created in FormAssembly, but there are also many more! Almost any information gathering need can be fulfilled by creating a form in FormAssembly.

Getting Access to FormAssembly

Before you can begin creating forms with FormAssembly, you must request access to the service.  To request access please complete the form here: Your request will be processed and you should receive a response within three business days. 

FormAssembly Location

Once you are notified that you have been granted access to FormAssembly you can access it by visiting this address:  Login with your uniqname and LAN password.  Now you’re ready to start creating forms!

Getting Started With FormAssembly Checklist

These steps will help you get started with FormAssembly:

  1. Request access to FormAssembly by visiting:
  2. Review the regulations and suggestions for working with Private Personal Information by visiting Ann Arbor's Privacy Tips:  and looking over the information in this Quicknote.
  3. Review the Best Practices Guide for Information Collection and Manipulation in the section below.
  4. Once you get your log-in information, log in at
  5. Create your first form!  Make sure it is SSL enabled.
  6. Share your form by sending users the URL OR by embedding it in a page on your departments branch of the content management system.
  7. Review your responses.

Best Practices Guide for Information Collection and Manipulation

To make sure you know what information is considered personal or private, please refer to the guidelines listed below. These guidelines, and more information on how to safely work with personal information, can be found at:

Introduction – What is Personal/Private Information?

Identity theft is a very real threat in today’s technology dependent society.  UM-Flint employees must do their part to avoid endangering personal information.  To help the campus community towards this goal, ITS provides this guide to advise users on some safety measures that should be employed when working with electronic forms.  It is also recommended that form designers refer to UM-Ann Arbor’s Privacy Tips.  This guide is not designed to cover every legal aspect of gathering personal information by electronic means, but merely to begin to educate form designers.

Private Personal Information (PPI) is any information about a person that can be used to identify, contact, or locate the person.  All of the items listed below are considered Private Personal Information and should be treated as highly confidential, especially when gathered together:

  • Full Name
  • Address
  • Birth Date
  • Gender
  • SSN (or other national identification number)
  • Driver’s License Number
  • Credit Card Number
  • Student Records
  • Patient Health Information that can be used to indentify an individual
  • Human Subject Research that can be used to identify an individual

The above list outlines some examples of PPI, but there may be others not included on the list.  When creating your form, ask yourself – could I use this information to identify, contact, or otherwise locate this person?  If the answer is yes, you’re working with PPI.

Collecting PPI – Do you really need it?

When creating your form you should make every effort to only require information that is absolutely necessary.  For example, if you aren’t sure you’ll ever need to know the user’s birthdate – don’t ask for it.  Storing PPI that will never be used places it at an unnecessary risk – even when the most strict security guidelines are in place.

Accessing and Saving PPI

When it is necessary to gather PPI employ these tips to keep the information safe:

  • Don’t export response results from FormAssembly unless it is absolutely necessary to work with the data.
  • If you must export response results make sure they are stored in a secure location and don’t leave multiple copies lying around.
  • Do NOT store files containing PPI on departmental drives or where unauthorized persons could potentially access them.
  • After you are done working with exported results delete them as soon as possible using one of these secure methods for deletion:
    • For Windows computers:
    • For Mac computers:
      • Use “Secure Empty Trash” command.
      • Use file shredder software such as ShredIt.
    • If you must make paper print-outs of PPI make sure that they are properly disposed of – cross-cut shredders are the preferred method.  Do not leave print-outs lying around a meeting room after they are used.
    • Don’t discuss PPI in public areas where other people might hear your discussion.

Additional Information

FormAssembly is a wonderful solution to creating forms, but it might not be right for everyone. If your form requires some form of authentication (for example, asking students to log in using their UMID/SIS PIN before filling out the form) or if you need a complicated back end for data management – FormAssembly isn’t for you.


If you have any questions or experience any issues with this Quicknote, please visit or contact the ITS Helpdesk for assistance.

Locations: 206 Murchie Science Building or 3174 William S. White Building
Phone#: (810)-762-3123 (option 1)
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found