A JHED ID can be used across multiple Johns Hopkins resources, but one successful sign-in does not necessarily create access everywhere.
This distinction is important because institutional systems often have several separate layers: identity, authentication and authorization.
Identity
Your JHED ID identifies the account associated with you in the Johns Hopkins environment.
Authentication
Authentication is the process of proving that you are the person associated with that identity.
This may involve credentials and current security requirements such as multifactor authentication.
Authorization
Authorization determines what you are allowed to do after authentication succeeds.
An application may require a specific role, department assignment, academic status, training requirement or administrative approval.
This is why a user can sometimes log in successfully but still be unable to open a particular application.
The three-layer troubleshooting model
When access fails, ask:
Do I have the correct identity?
If the JHED ID itself is unknown or incorrect, start with identity support.
Can I authenticate?
If credentials or MFA are failing, investigate authentication.
Am I authorized for this application?
If sign-in succeeds but the application denies access, the issue may belong to the application’s permissions.
This model can prevent users from repeatedly resetting passwords when the real problem is an application entitlement.
JHED is used by systems with different purposes
The same identity can appear in academic, administrative, communication and workplace systems. Official materials also show JHED authentication being used as part of access to specialized systems.
The identity is shared. The permissions are not necessarily shared.
Internal Link Suggestions:
- What Is JHED?
- JHED Access Problems: A Troubleshooting Framework
- JHED Access for Students, Faculty and Staff
Sources: Johns Hopkins myJH Support; BSPH Web Help Desk; Johns Hopkins faculty system documentation.