Students, faculty and staff may all have JHED identities, but they do not necessarily use the identity in the same way.
The JHED environment is shared across a large institution. The resources connected to a particular user depend on the person’s role and institutional relationship.
Students
Students may encounter their JHED ID during onboarding and use it to reach institutional resources connected with academic life.
The same identifier can be relevant to email and academic systems.
Faculty
Faculty may use JHED credentials in teaching, roster, grade-reporting or other institutional workflows depending on their assigned systems and responsibilities.
Access to a faculty-specific application can still depend on the application’s separate authorization model.
Staff
Staff may encounter JHED as both a directory resource and an institutional identity used for workplace systems.
The resources available can vary significantly by department and job function.
The key lesson
A shared identity does not mean a shared permission set.
Two people can both have valid JHED IDs while seeing entirely different applications and resources.
This is normal in a role-based institutional environment.
When comparing access, compare roles—not just usernames
If one person can access a system and another cannot, the difference may relate to:
- role;
- department;
- enrollment or employment status;
- required training;
- administrative approval;
- system-specific permissions.
The correct troubleshooting question is therefore not always, “Does this person have JHED?” but rather, “What does this particular role need in order to access this particular system?”
Internal Link Suggestions:
- How JHED Authentication Works Across Systems
- JHED Access Problems
- What Happens When a JHED Affiliation Changes?
Sources: Johns Hopkins Engineering Support; Hopkins EP Online; Johns Hopkins faculty resources.