C11. Custom User Fields

Prev Next

Ways to Apply

Standard accounts collect name, date of birth and contact details. If you need something else at account creation, such as a school district, a membership number from a partner program or an employer, custom user fields let you collect it. They're simple to build, but the choices you make about field type, required or optional, and what to do about answers that don't fit can create problems every customer meets once. Think of Custom User Fields as questions that become part of the customer's permanent account record.

Examples include:

  • School District

  • SilverSneakers Number

  • Military Status

  • Residency Verification Method

Important Note:

When creating Custom User Fields, you do not want to gather Personally Identifiable Information (PII), Sensitive Personally Identifiable Information (SPII), and Protected Health Information (PHI) that may go against your local or state policies within the software such as Social Security numbers. For more information, please refer to our Help Center article PII, Sensitive PII and PHI.


Video Lesson

To learn more, please watch our instructional video to learn about Custom User Fields. Once finished, review how you can apply what you learned in the system before continuing to the next lesson, Scholarships.


Need Help?

View answers to questions frequently asked by users in our Frequently Asked Questions or contact your CivicPlus representative if you have additional questions. Alternatively, you can review Tasks to Complete to see tasks that you can implement in your system on your own as well as Best Practice suggestions for implementation of Custom User Fields.


Frequently Asked Questions

Where in the system can I view Custom User Field responses?

Custom User Fields may appear:

  • During Account Creation

    • Customers complete fields while creating their account.

  • During Account Updates

    • Customers update information in Custom User Fields as needed.

  • Within Staff Account Management

    • Staff can review and edit information.

  • In Reports

    • Field data can often be reviewed for operational purposes.

    • Because the information becomes part of the account record, it remains available for future registrations.

What about existing accounts when I add a required field?

A newly created field will appear on the account as unanswered. Customers will need to be notified about the new field so that they may complete the required information. Consider creating a notification procedure for newly created fields.

What's the downside of putting too much on the account form?

Every new customer sees it. A long account form costs sign-ups. Collect only what you need on day one, and ask the rest as prompts at registration.

Can Custom User Fields be tied to Addons and Discounts?

No. Custom User Fields cannot be tied to Addons and Discounts. If you wish for an addon or discount to apply based on an answer, please see our module about Creating Prompts.


Tasks to Complete

These tasks give you hands-on practice with custom user fields in your own Recreation Management system, so you can see how it behaves before your customers do. You don’t need to complete every task. As you go, note any questions and bring them to your CivicPlus representative.

Custom User Field Tasks

  • List what you need at account creation, and for each choose custom field, prompt or Organization Option.

  • Decide required or optional.

  • Plan the options for choice fields, including 'Other'.

  • Create each field with a clear label and type.

  • Set maximum length where it applies.

  • Create an account and see each field.

  • Fill a field in, then check it in a report.

  • Try a customer who doesn't fit any option.


Best Practices

Please consider some of our suggestions for applying best practices in the Recreation Management software. It is essential to evaluate your current processes and identify areas where improvements can be made. By doing so, you will not only streamline your workflow, but also provide a better experience for both staff members and public users.

Best Practice Recommendations

Use these recommendations to evaluate your current processes and find where small changes can make this feature easier for your team and your customers. They are suggestions, not requirements, so adopt the ones that fit your organization, and build the habits early, before the system is in daily use.

  • Collect only what you need at account creation

  • Check Organization Options before building a field

  • Prefer choice fields for reporting

  • Include 'Other' in required choice fields

  • Keep labels short

  • Fill a test account before reporting

  • Don't collect sensitive data in a field

  • Test the account form

  • Review fields yearly

Recommended Launch Checklist

Use this checklist as a final review before your team and your customers start relying on this feature, to confirm nothing has been missed. It’s a last check, not a setup guide, so if an item isn’t complete yet, return to the tasks and best practices above before you launch.

  • Limit fields to information that provides value.

  • Use dropdowns whenever possible to maintain consistent and valid information.

  • Keep account creation simple. Not all information needs to live permanently on an account. Use prompts to gather registration relevant information.

  • Review fields annually to ensure data stays relevant.

  • Avoid duplicate data collection. If the information is already a prompt, it may not need to also be a field. Prompts and Custom User Fields can be both added to various reports.

  • Coordinate field creation with department leaders.

  • Test reporting before launch.

  • Align fields with residency, discounts, and membership workflows.

  • Train staff on field usage and maintenance.


Initial Missteps

Please review initial missteps that are common with the implementation of custom user fields to avoid issues when the feature is used. Please keep track of any questions you may have so your CivicPlus representative may address them.

Mistake

What Happens

Do This Instead

Requiring a choice with no 'Other'

Customers can't create an account with accurate information.

Add 'Other'.

Collecting sensitive data

Anyone with account access sees it.

Use documents.

Vague labels

Customers guess.

Use plain labels.

Not testing from the public side

Surprises.

Test it.