Configuring NeonCRM

Configuring NeonCRM



This is the first video someone looking for a grounding in the basics of Neon should watch. This video will cover topics related to using this software as a System User or System Administrator. In particular, it covers the ways people access Neon (Constituent Login Portal and System User and Administrator login) and how to restrict what System Users can access. Additionally, it covers where to store key pieces of information about your organization (The Organization Profile) and your constituents (Account Standard Fields and Account Custom Fields). Lastly, it covers some foundational settings related to conducting transactions (Payment Gateway, Tender Types, and more). 

Instructional Video


  • Constituent: an individual or organization that interacts with you
  • System User: anyone with a login name and password to access the “back end” or administrative side of Neon
  • System Administrator: system user with access to the System Settings module
  • User Group/Permissions: a set of options meant to restrict access to certain aspects of NeonCRM to certain System Users
  • Login Page: the URL where constituents can access the constituent login portal and system users can access the back end of Neon
  • “Back End” of Neon: Neon’s user interface for system users and administrators
  • “Front End” of Neon: web pages available to the public and/or constituents
  • Account: a record of a constituent
  • Account Standard Field: a type of input field that exists by default; available to capture attributes of Organization and Individual Accounts via forms
  • Account Custom Field: a type of input field that a System User has created; available to capture attributes of Organization and Individual Accounts via forms
  • Tender Type: the form of the money (check, cash, etc)

Video Contents and More Information


System Users and Permissions

Organization Profile

Account Fields

Payments and Transaction Settings

 Constituent Login Portal

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk