A watch flag is a custom interaction that displays a yellow bar across the top of a person record, indicating an important message about the person. Examples include:
VIP
A child of a faculty member
A local celebrity
Academic integrity violation
Early alert
Any other high-level data that should be the first thing users know about the person
When added to a record, the watch flag persists above all tabs. Watch flags can also be added to dataset records.
Creating the watch flag interaction code
Go to Database → Activity & Interaction Codes.
Select Insert.
Configure the following settings:
Status: Set the status to Active.
Folder: Keep your codes organized by putting them in a folder. Select Other to create a new folder.
Type: Select the type of interaction.
Code: Use the code
FLAG.Parent Code: Leave this setting blank.
Label: Enter the display name of the interaction.
Select Save.
Custom interactions vs. subcodes
There are two main approaches to watch flags: allowing your staff to write their own custom interactions on each individual record, or using a standard set of subcodes shared across your instance.
Using custom interactions
Go to Lookup.
Search for and select a record.
Select the Timeline tab of the person record.
Select Interactions → New Interaction and configure the following settings:
User: This defaults to the current user.
Code: Select the watch flag interaction you created earlier.
Timestamp: This defaults to the current time, but the value can be overridden. The timestamp is not shown in the yellow bar.
Subject: Enter the text that should appear in the yellow bar.
Comments box: Leave this setting cleared.

Select Save.
Using subcodes
If you have a standard set of watch flags for your staff to use, you can create them as subcodes of the main watch flag interaction.
Creating watch flag subcodes does not prevent staff from selecting the main watch flag code and writing their own custom interaction. You can audit for these interactions by querying for watch flag interactions that do not have a subcode selected.
Go to Database → Activity & Interaction Codes.
Select Insert.
Configure the following settings:
Status: Set the status to Active.
Folder: Keep your codes organized by putting them in a folder. Select Other to create a new folder.
Type: Select the type of interaction.
Code: Use a unique code. For this example, use
integrity.Parent Code: Select Watch Flags, the parent watch flag created earlier.
Label: Enter the display name of the interaction.
.png?sv=2022-11-02&spr=https&st=2026-05-11T17%3A31%3A41Z&se=2026-05-11T17%3A44%3A41Z&sr=c&sp=r&sig=7ybh2INfzREAl8Wf9MxUVZAeZ7HEBmTuuWQ9j5N8veM%3D)
Select Save.
Multiple watch flags
There is no limit to the number of watch flags that can be added to a record. The watch flags appear in a list with semicolons between each flag.
Watch flags for Student Success
Watch flags can help advising, faculty, coaching, and support teams identify concerns that should be visible immediately on a student record. Common examples include:
Identifying students who may need support: Add a watch flag when a student may be having academic difficulty, missing multiple classes or assignments, or falling behind in coursework.
Monitoring progress: Use watch flags to track students who are currently enrolled in specific programs or courses and need focused follow-up throughout a term.
Supporting early intervention: Alert advisors, coaches, or other staff when a student shows signs of struggling with a course, assignment, or related requirement.
Improving communication: Use watch flags to help faculty and support staff share high-priority context, such as when a student needs targeted outreach.
Watch flags work best when the flagged concern is important enough to appear before staff review the rest of the record. For more detailed follow-up, use the watch flag with related notes, tasks, communications, or other Slate records that document the next action.
Automating alert communications
Deliver can automate alert messages through rules or administrative actions. Automated messages can notify specific users that a follow-up action or intervention step is required.
For example, an email can be triggered from a custom field that stores information about disciplinary action. The recipient list filters can identify the appropriate information and send the email to the correct staff member, prompting them to take action.



