In this article
Use MyUNT for the relevant student-administration task, Canvas for course activities and materials, and EagleConnect for university email. When something is missing, first name the system where it is missing. Similar-looking symptoms can need different kinds of help.
Three systems, three kinds of evidence
UNT identifies Canvas as its learning management system and EagleConnect as its official email system. MyUNT is the student-information portal. These broad roles help you locate a question, but they do not guarantee that every detail is instantly reflected in every system or that every instructor uses course tools in the same way.
An enrollment question concerns the administrative record. A question about an assignment concerns the course and its instructions. A question about whether you received a university message concerns email access or the sender’s communication. The systems can relate to one another without making the evidence interchangeable.
Finish the sentence “missing from…”
Instead of saying “my class disappeared,” complete the sentence: missing from the current official schedule, missing from the course-materials view, or missing from an expected message. That extra phrase gives the next person a place to start. It also helps you avoid changing enrollment to solve a course-content question.
Then add what you expected to see and why. Did an official action confirm a change? Did an instructor say a resource would be available? Did an office say it would send a message? Keep the basis for the expectation visible. “I thought it would be there” is a useful feeling to notice, but it is not the same as a stated instruction.
| Observation | First clarification |
|---|---|
| A section is absent from a schedule. | Which term and enrollment state are shown? |
| A course resource is unavailable. | Which course tool and specific resource are involved? |
| An expected message cannot be found. | Which mailbox and expected sender or subject are involved? |
| Several services cannot be accessed. | Is this an access issue that belongs with technical support? |
Do not turn a delay into a diagnosis
If information differs across systems, describe the difference before deciding its cause. A discrepancy could require technical support, a course-level clarification or an administrative correction. This publication cannot inspect your private account or determine which applies.
A useful note says when you observed the difference, what action preceded it and which views disagree. Avoid declaring an outage based only on one unsuccessful attempt. The official IT HelpDesk links service-status resources; consult the relevant current information there if needed. This article is not a live status monitor.
Hypothetical example: the missing materials
A student confirms a section on the current official schedule but cannot find an expected resource in the course-learning environment. The student asks about that resource and its availability instead of submitting a new enrollment request. The distinction keeps a course-content question from becoming an unnecessary administrative change.
Make an inbox review task-based
An email can inform, request action or confirm something already done. Read for the verb and the destination. Does the message ask you to review instructions, complete a task in an official system, attend an appointment or simply note an update? A message’s arrival is not completion of the action it describes.
Keep a short action note with the official destination rather than leaving every unfinished item hidden in an unread inbox. If a request is unexpected, verify it using a known university route before supplying sensitive information. Do not rely on the display name alone or send authentication codes by email.
EagleConnect’s current official information should govern access questions and service details. Avoid relying on old advice about forwarding, storage or account availability; those policies and interfaces can change. This guide uses the service’s role, not a permanent promise about every feature.
Route course questions with enough context
For an assignment or resource question, use the instructor’s stated communication channel and identify the relevant course item. Explain what you read and the point that remains unclear. Do not send a broad technical complaint if the actual question is whether a particular instruction applies to your work.
For a technical issue, distinguish failure to access a system from failure to find one item after access succeeds. The first and second can require different investigation. A concise description of what does work can be as helpful as the error itself because it narrows the problem without claiming a cause.
Keep identity and access private
This website has no connection to your university accounts. Its local planning tool does not ask for your EUID, student number, email address or password. Do not paste account details into an editorial message or share screenshots of unrelated records merely to explain which system you mean.
If official support requires identifying information, use its approved channel. A public description can begin with the service, device category, approximate time and sanitized symptom. The support-note guide provides a structure for that first message.
Check the right result before closing the issue
If the problem was an enrollment state, verify the administrative state. If it was access to a course resource, verify that resource. If it was an email issue, verify the relevant email function. Fixing one symptom does not prove that every related process is complete.
Use the MyUNT task map to reconnect the issue to your wider administrative work. If a schedule change was involved, return to the schedule-state guide. Keeping the systems distinct is not extra bureaucracy; it is a way to ask a smaller, more answerable question.
Sources & scope
Public official sources checked October 25, 2026. The organizing methods and labeled hypothetical examples are original editorial work, not university procedures. No private student account was accessed. Current official instructions govern individual actions.