Automated tagging allows you to automatically apply tags to applications to support your program management. Tags can be applied based on:
- The option(s) an applicant selects in an optionable field, or
- A specific trigger event in Good Grants
Both methods can be used together depending on your workflow.
Auto-tag based on an optionable field
Optionable fields include drop-down lists, radio buttons, and checkbox lists. This method is commonly used to:
- Track demographics
- Allow applicants to express interest in multiple categories
- Auto-classify applications during submission
To configure automated tagging from a field:
- In the Manage workspace, go to Applications
- Click Edit form and choose your form
- Create or edit an optionable field (see: Add a form field)
- In the 'Options' section of the configuration tray, toggle on Auto-tag
- Enter the tag you want applied for each option
- Click Save
When the applicant selects an option, the tag will be applied using the option’s value.
Auto-tag based on a trigger
Good Grants provides a set of system events that can automatically apply tags when they occur.
To set up automated tagging based on a trigger:
- In the Manage workspace, go to Settings > General > Tags
- Click Add tag to create a new tag, or open an existing tag
- Under 'Automatically apply tag when', select the event that should trigger the tag
- Click Save
The tag will now be added to any application when the selected event occurs.
Available triggers
These events can automatically apply a tag when they occur.
Application activity
- Application submitted – the application is successfully submitted
- Application archived manually – the application is archived by an administrator
- Application resubmitted – a previously submitted application is updated and resubmitted
- Application tagged – the application receives any tag
Payments
- Payment success – payment is completed
- Payment pending – payment is initiated but not completed (e.g. invoice or offline payment)
Action stage
Triggered by any of the following:
- An action stage starts
- A reviewer clicks Proceed
- A reviewer clicks Stop
Use case: If you use multiple action flows for the same application, action statuses may become difficult to filter. Since the Applications view only filters by one action status, use automated tags when an action stage starts or when a reviewer selects Proceed or Stop. Tags allow you to filter consistently, even when applications hold multiple action statuses.
Moderation
Triggered by moderation outcomes:
- Approved
- Rejected
- Undecided
Duplicate management
Triggered when managing duplicates:
- An application is marked as the primary application
- An application is marked as the secondary duplicate and archived
Reviewing
- Assignment completed – a reviewer completes their assignment for the selected score set
Good to know
- Tags applied automatically are management-only and not shown to applicants or reviewers.
- Optionable-field tags use the field’s value, not its label.
- Automated tagging works well with complex workflows and multi-stage reviewing.
- You can remove or update automatic tag rules at any time.
- Tags can be combined with filters, panels, and exports to streamline program operations.