Configuring Behavior and Student Comments

As of July 12, 2021, this "Learn Veracross" site has been deprecated.  It will remain live through December 2022, but will no longer be updated. All knowledge content has moved to the new Veracross Community.  Please update your bookmarks.

Here is the new version of this article in the Veracross Community.


Behavior Events and Student Comments require the initial configuration of many elements in Axiom.  To understand what configuration is needed, see the details below.  If you wish to implement this functionality at your school, please complete the Behavior & Comment Workflow Questionnaire.

Dropdown Menus

On Behavior Events and Student Comments, there are four fields for which the values can be customized for your school. Each field is outlined below.

Incident Types

The incident type explains why a behavior event has been entered (e.g. disrespect toward a teacher, dress code violation, etc.). Each incident type can be configured to allow or not allow teachers to input events with this incident type.

Outcome Types

The outcome type explains what the result of the incident is (e.g. Detention, Call home, etc.). Each outcome type can be configured to allow or not allow teachers to input events with this outcome type.

Comment Types

The comment type explains what the purpose of the comment is (eg. General comment, Good participation, Performance concern, etc.). Each comment type can be configured to allow or not allow teachers to input comments with this type.

Status/Follow Up Status

The Behavior/Comment Status and Behavior Follow Up Status help to track the process of the behavior or comment.  The status and follow up status can be used by the user entering the comment or by those who are following up on the event/comment. Examples of statuses might be:

Status: Pending, Awaiting Outcome, Closed

Follow Up Status: Not Needed, Needed, Complete


Within the teacher portal schools can configure what they want faculty to be able to do with behavior events and comments. Each section of the behavior and comments input screen is explained below.

Add a Behavior Event form

There are three parts to the behavior event form that show up when a teacher inputs a Behavior Event. The outcome section can be turned off if desired.

1. Student and Class section – includes the student and class fields which will automatically display the student homeroom and parents once a student has been selected

2. Incident section – will show the incident, incident date, and incident notes

3. Show Outcome section – will show outcome type, date, notes and assigned to fields. This section    can be turned off.

Add a Student Comment form

1. Student and Class section – includes the student and class fields which will automatically display the student homeroom and parents once a student has been selected

2. Comment section – will show the comment type, date, and the comment itself in this section.

Faculty Security

  • The Division_Head_0 through Division_Head_3 security roles grant users access to view or edit all behavior and comments.
  • The Head_of_School security role grants users read-only access to all behavior and comments.
  • All three faculty security roles grants access to behavior events for any student that is in one of his/her classes, regardless of whether or not the class where the behavior incident/comment occurred is taught by the teacher.
  • The Behavior_Reader security role gives read-only access to Behavior/Comment data for all students whose school level matches one of the user’s school levels. This match is based on matching person_classification records by school level.
  • The Behavior_Admin security role gives full read-write access to Behavior/Comment data, and respects the user’s school levels in the same way that Behavior_Reader does.

The teacher portal only has the option for teachers to see behavior events for the students they teach or their advisees. There is no need to request special security for hiding behavior from other students.

Parent & Student Security

The parent and student portals will not show behavior events or comments.

Notification/Review Workflow

A school’s notification process for behavior events and comments can differ.  In order to accommodate differences in work flow, there are multiple notification types to be configured. After a behavior or comment is entered, internal notification will automatically be sent and public notification can be selected.

Internal Notifications

Internal notifications are for advisors, teachers or other staff at the school. The logic for who should receive internal notifications when behavior events and comments are entered for a student is configured upon setup of this functionality. For example, schools might want both the division head and advisor notified when a teacher enters a behavior event for a student.

The internal notifications are all configured upon setup of this functionality and are not something selected or chosen upon entry of a behavior or comment. To setup internal notifications, add a new Notification Configuration record from the system homepage and set the person to be notified along with the details of which comments/behavior should trigger the notification.

Public Notifications

Public notifications are for parents and students only. When notification is sent to parents and/or students regarding a behavior or comment (this is optional), an email is sent.  From the behavior and comment records, the notification template can be selected if the notification options are chosen.

Email Templates

There are different email templates used for sending behavior and comment notifications internally and publicly. Learn more about configuration of these email templates.

Frequently Asked Questions

  • Can parents/student respond via email or the portals to a behavior or comment?
    • No