Editing Proposal Notifications
There are 7 separate notifications that could be sent when using the Proposal Workflow process. School Administrators can customize each and tailor them to specific school processes, for example - using a formal administrative signature block on approval notifications. In addition to custom text, specific attributes from Proposal records can be merged into notifications (e.g., Proposal Name, Proposal URL, author email).
Course Management → Academic Administration → Notifications
For the Graduate-level CC-GS-GSAS Proposal Workflows, there are 7 additional notifications that will be used. Graduate-level Course Proposals will be routed to a “secondary” Reviewer and the GSAS COI is considered a “secondary” Approver. CC/GS/GSAS Notifications are managed under the School of Arts & Sciences bucket.
Default Notification templates are set the Columbia University-level and can be edited / customized by each school. Notifications sent are determined by the school of the Author submitting the Proposal (e.g., if a course proposal is co-owned by Barnard and CC/GS, the CC/GS notifications will be used).
Uncheck 'Use default text' to submit custom text.
+ Add dynamic text allows you to merge Proposal attributes into the email
