Link rot
Old URLs 404 mid-term.
Google Docs Connector lets teachers attach Docs/Slides/Sheets from Drive next to lesson plans and assignments so students open the right file without hunting shared links.
Teachers paste links in WhatsApp; permissions break; students submit the wrong copy.
Old URLs 404 mid-term.
“Request access” storms.
Files float outside the lesson.
Students edit the master doc.
Operational depth your team will use every cycle — not a shallow feature list.
Attach files/folders to lessons & homework.
Launch Docs from ScholarERP cards.
Warn when a file is private.
Optionally distribute per-student copies.
Store Drive links in Learning Resources.
Works smoothly with Google SSO.
See who linked what.
Remove stale attachments cleanly.
A clear path your staff and parents can follow without training manuals.
Teacher selects a Drive file.
Bind to lesson or assignment.
Ensure class can view/copy.
Students open from the portal.
The right people see the right slice of the pipeline.
Links Drive to plans/homework.
Works from Student Portal.
Controls Google connector scopes.
Sees attached materials coverage.
Each module is an edge in the campus operating graph — not a silo.
Measurable ops wins institutions report once this module runs inside ScholarERP.
“Attaching Slides to the lesson card ended “ma’am link please” messages before every period.”
Straight answers for setup, integrations, and day-two operations.
Typically no — ScholarERP stores references and opens Drive with Google permissions.
Yes for assignment templates where configured.
Yes for Docs/Drive connectors.
No — Learning Resources can hold many file types; Docs Connector deep-links Google-native files.
Pick from Drive, bind to a lesson, open as a student.