Digital Media Discord
Case study · AI Tools & Strategy
Research and rationale for a closed student community that connects our digital media programs where students already are, with critique, tutoring, faculty, announcements, and a daily jobs agent inside one Discord server.
Our digital media Discord server runs as a closed, cross-program community, connecting students across our courses and giving them a place to critique, connect, and find opportunity in a space they already live in. This page explains why it exists, how it works, what the research says, and how we keep it clear of FERPA-protected data.
The problem it solves
Canvas discussion boards are bad at community. Students upload to a thread, see a few classmate posts, and move on. There is no cross-course visibility, no informal channel, no place where a second-semester student can hear from a student who just graduated. Support like tutoring stays siloed in a separate system that students have to seek out on their own, usually under stress.
At the same time, our students are already using Discord. Not for academics, for gaming, design communities, and peer networks. The platform is familiar, notification-native, and built for media sharing: images, links to video and animation work, screen sharing, voice. It handles exactly what Canvas discussion boards handle poorly.
We chose Discord because students were already there. The goal was not to introduce a new tool, it was to build a light structure around something that already existed in their daily lives, and put a few useful things inside it.
What we built
The server is closed, not discoverable by the public, and join-by-invite only. Students opt in. They can use display names rather than their legal names, which creates a layer of practical privacy. No grades, no enrollment records, no FERPA-protected data is ever shared inside the server. It stays a co-curricular community: a place for peer critique, announcements, and connection across all of our digital media programs, not a course-record system.
Right now, three things sit inside it alongside the students:
- Our department tutor. Our own program tutor is present right in the community’s channel. the college’s central tutoring also runs on Discord, on its own separate server, so it is the same familiar tool in a different place.
- Faculty across the programs. Full-time faculty are in the server, which is why this is a faculty collaboration rather than any one person’s project.
- A daily jobs agent. An AI agent runs every day, finds a few verified entry-level jobs and internships in the students’ fields, and posts them right in the channel, so real openings come to students where they already are. It collects no student data.
That is the real current state: a student community with critique, a department tutor, faculty presence, announcements, and the jobs agent. It is closer to a student club Discord than to anything institutional, and it is kept deliberately simple.
What the research says
A pilot with 300+ first-year Computer Science students found engagement in Discord cohorts far outpaced previous years relying on a standard VLE. Benefits included peer support, social connection, and community, things the LMS could not provide.
A study of undergraduates using Discord in online social science courses found the key benefits were connecting students to each other and to faculty, building community, sharing course information, and establishing a casual, informal learning environment. Challenges were reported far less often than benefits.
Presented at the institutional level, “Using Discord to Improve Student Communication and Engagement” documents a systematic implementation and positive outcomes in student communication and community.
Research on adult learners at community colleges using the CCSSE benchmarks found that each engagement benchmark, including support for learners and student-faculty interaction, individually increased the likelihood of retention. Connecting students to support is not supplementary, it is the work.
Documents Discord servers at the institutional level: clear channel organization, defined roles, and explicit community norms drive results more than platform features. Structure matters more than software.
A fellow Maricopa college built a Discord-based virtual help desk for its computer lab and won a district MCLI Innovation Award for it. Their write-up notes Discord was already where students gathered, and that other Maricopa instructors asked for help setting up their own servers. Within-district, district-recognized precedent.
FERPA and how we handle it
FERPA protects “education records,” information that is personally identifiable and maintained by the institution. It does not prohibit students from talking to each other. The real concern is that Discord is not a FERPA-compliant vendor (it holds no data processing agreement with educational institutions), which means the institution should not use it to transmit or store education records. We do not.
| Activity or data type | FERPA status | How we handle it |
|---|---|---|
| Grades, enrollment status, transcripts | Protected | Never shared in Discord. Grades stay in Canvas and institutional systems only. |
| Student real name plus course enrollment, visible together | Handled | Students are told they do not need to use their real names, and the syllabus carries a disclaimer explaining this and what FERPA is. Enrollment is not referenced, and names and sections are not cross-referenced inside the server. |
| Past-semester critique posts visible to current students | Handled | Courses are archived semester by semester, so previous-semester student work is not left visible to current students. |
| General announcements, events, job postings | Not protected | Standard content, no PII involved. This is the bulk of server activity, including the daily jobs agent. |
| Student-to-student peer critique and conversation | Not protected | Voluntary and student-initiated. No institutional data. This is co-curricular community, not course records. |
| Tutor presence | Not protected | Staff acting as community resources, not maintaining records inside Discord. Referrals happen, records stay in institutional systems. |
The strongest FERPA argument: this server is a co-curricular community, not a course-record system. It is closer to a student club Discord than to a Canvas gradebook. The institution does not maintain it and does not own the data. Students opted in voluntarily and can participate pseudonymously. Comparable to a student using a public platform to post about their coursework, the fact that a faculty member is aware of it and encourages it does not make it an education record.
Precedent runs deep: EDUCAUSE, Inside Higher Ed, and multiple peer-reviewed studies document institutional Discord use at this scale. CU Boulder’s OIT explicitly acknowledges Discord as a student-used platform and has published guidance for server administrators rather than banning it outright. The University of Southampton ran a department-level Discord pilot of 300+ students with institutional awareness.
The connection to connectivism
The theoretical foundation is George Siemens’ connectivism, the idea that knowledge is distributed across networks of people, tools, and resources, and that learning happens through the connections we make and maintain. Traditional instruction delivers content to students. Connectivist design gives students a network and asks them to participate in it.
The Discord server is not a supplement to courses. It is a learning environment in its own right, one where students encounter the informal knowledge, professional norms, and industry connections that courses alone cannot provide. A second-semester student seeing how a graduating student approaches job searching is a learning event. A first-year student getting help from a tutor in a public channel, where other students can see and learn from the interaction, is a learning event. These do not happen in Canvas.
Both Render (student career tool) and Cultivate (faculty PD system) are also connectivist designs: personal learning environments where the individual constructs and maintains their own knowledge infrastructure. The Discord server is the community layer, the network that connects those individual systems together. Graduate research on connectivism and personal learning environments is the intellectual foundation for all three.
References
- Bills, O. (2021). Discord pilot with first-year Computer Science cohort. University of Southampton. As reported in: Discord’s growing relevance in the education sector. Jisc Co-Design. https://codesign.jiscinvolve.org/wp/2021/10/discords-growing-relevance-in-the-education-sector/
- Lauricella, A. et al. (2024). Examining the Benefits and Challenges of Using Discord in Online Higher Education Classrooms. ResearchGate. https://www.researchgate.net/publication/377107344
- Schwartz, D. (2021). Using Discord to Improve Student Communication and Engagement. UNLV Best Teaching Practices Expo. 122. https://oasis.library.unlv.edu/cgi/viewcontent.cgi?article=1095&context=btp_expo
- Siemens, G. (2005). Connectivism: A learning theory for the digital age. International Journal of Instructional Technology and Distance Learning.
- Spitzig, J. (2021). The Relationship Between Student Engagement and Student Retention of Adult Learners at Community Colleges. Franklin University, Doctoral Dissertation. https://fuse.franklin.edu/docpub/26/
- SAGE Scholars. (2023). Using Discord to Build Campus Community. Tuition Rewards Blog. https://www.tuitionrewards.com/newsroom/articles/594/using-discord-to-build-campus-community
- EDUCAUSE. (2014). Is Your Use of Social Media FERPA Compliant? EDUCAUSE Review. https://er.educause.edu/articles/2014/2/is-your-use-of-social-media-ferpa-compliant
- Wernz, J. (2013). Are Emails, Texts, Tweets, and Other Digital Communications Student Records Under FERPA and State Law? Education Law Insights, JDSupra Business Advisor.