Proponents
Proponents are applicant/recipient profiles. They can be created before agreements, reviewed independently, assigned to teams, and linked to one or more agreements.
Setup Dependencies
| Dependency | Why It Matters |
|---|---|
| Lead agency | Every proponent is led by one agency. The lead agency controls reference data and many permission checks. |
| Proponent subtype | The subtype must be configured under the lead agency before the profile can be created. |
| User roles | Users need proponent permissions before they can create, update, delete, review, or manage team membership. |
| Review setups | Reviews appear only when eligible review-set setups exist for proponent records. |
| Agreement setup | The Agreements tab becomes useful after programs, streams, agreement subtypes, and agreement permissions exist. |
List Page
The Proponents page supports search, status filtering, pagination, column controls, and row actions. Search is intended to help users find a profile by identifiers, legal names, operating names, subtype, or lead agency.
Create opens the proponent create page. Edit opens the detail workspace. Delete is a soft delete and removes the proponent from normal active lists without erasing historical references.
Create Profile
The create page starts a draft profile. Users choose the lead agency and proponent subtype, then enter bilingual names, descriptions, identifiers, and NAICS information.
| Rule | Behaviour |
|---|---|
| Lead agency is required | A proponent cannot exist without an agency owner. |
| Subtype is required | The subtype classifies the proponent and must belong to the lead agency. |
| NAICS is required on create | The profile must include the industry classification needed by reporting and review workflows. |
| Business number must be unique when provided | Duplicate active business numbers are blocked to avoid duplicate organizational profiles. |
| New profiles start as draft | Users can complete supporting tabs before treating the profile as operationally ready. |
| Bilingual fields should be maintained together | Legal names, operating names, research organization names, and descriptions are displayed in the active language. |
Detail Workspace
The detail page contains a collapsible hero and route tabs:
| Tab | Purpose |
|---|---|
| General | Core profile, identifiers, agency, subtype, status, names, and descriptions. |
| Agency Financial IDs | Agency-specific financial identifiers. |
| Other Names | Alternate legal, operating, historical, or informal names. |
| Addresses | Physical or mailing addresses. |
| Contacts | People and communication details. |
| Reviews | Runtime review sets and assessment work. |
| Agreements | Agreements linked to the proponent. |
| Team | Users directly assigned to the proponent. |
Extension tabs can also appear when an enabled extension contributes a proponent tab.
General Tab
The General tab shows or edits:
| Field Group | Contents |
|---|---|
| Agency and classification | Lead agency, proponent subtype, and status. |
| Identifiers | Business number, charity number, provincial business number, and NAICS. |
| Bilingual names | Legal, operating, and research organization names in English and French. |
| Bilingual descriptions | English and French profile descriptions. |
When the current user can update the proponent, General is an inline edit form. Otherwise it renders read-only profile values.
Operational Flow
| Step | Action |
|---|---|
| 1 | Configure the lead agency and subtype reference data. |
| 2 | Create the proponent profile as draft. |
| 3 | Add identifiers, other names, addresses, and contacts. |
| 4 | Add team members if access should be delegated directly to users. |
| 5 | Run reviews when the business process requires a proponent assessment. |
| 6 | Link the proponent to agreements during agreement creation or from the agreement Proponents tab. |