The NCEdCloud IAM Service now offers the Alias ID feature, allowing users to log in using their email address, a local account name, or their 10-digit UID. Alias ID provides flexibility and convenience, enabling PSUs (Public School Units) to customize login methods for staff and students.

Key Features of Alias ID

  1. Flexible Login Options
    Users can log in with:
    • Email Address
    • Local Account Username
    • State UID (default)
  2. Password Unchanged
    The Alias ID does not affect the user’s password. Either the Alias ID or UID can be used with the same password.
  3. Opt-In Capability
    PSUs can choose to enable Alias ID for staff, students, or both by submitting the Alias ID Request Form.

Alias ID Options

1. Email Address as Alias ID

  • PSUs can use users’ email addresses from the IAM Service.
  • Steps to Enable:
    • Ensure all users have email addresses listed in the NCEdCloud portal.
    • Users without an email address can still log in using their UID.
  • Timeline: 1–2 weeks for implementation.
  • Advantages: Simple setup and minimal maintenance.

2. Local Account Username as Alias ID

  • Requires nightly file uploads with user details, including UIDs and unique local IDs.
  • Steps to Enable:
    • Prepare and upload a file with:
      • UID
      • Local username scoped for uniqueness (e.g., username@psuXXX)
      • LEA Code
      • Population Type (“Staff,” “Student,” or “Both”)
    • Coordinate with NCDPI and the vendor for file testing and implementation.
  • Timeline: 2–3 weeks, as it involves additional configuration.
  • Advantages: Customizable for PSUs with specific directory requirements.

FAQs

  1. What happens if a user lacks an email address?
    Users without an email address can continue logging in with their UID.
  2. Why can’t some users log in with their email addresses?
    • The email contains an invalid character, such as an apostrophe.
    • The email address is duplicated in another inactive or disabled record.
  3. Can users change their email address in NCEdCloud?
    No, email addresses are populated automatically from nightly source data (PowerSchool, LINQ HR, HRMS).
  4. What does “scoped to be unique across the state” mean?
    Local usernames must include a PSU-specific qualifier (e.g., username@psuXXX) to avoid duplication statewide.
  5. How frequently should data files be uploaded for the local username option?
    Files must be uploaded nightly for processing.

Implementation Steps

  1. Opt-In Request
    • Submit the Alias ID Request Form via the NCEdCloud portal.
  2. Configuration and Testing
    • For the email option, ensure all users have valid email addresses in the IAM Service.
    • For local usernames, coordinate with NCDPI and the vendor for SFTP folder setup and file testing.
  3. Go Live
    • Alias ID setup is finalized within 1–3 weeks, depending on the chosen option.

Note on Invalid Alias IDs

To ensure seamless login, the following validations are applied:

  • Apostrophes in email addresses or local usernames are not supported.
  • Duplicate Alias IDs will not be added.
  • The email or local username must already exist in the NCEdCloud system.

For further assistance, LEA Administrators can contact NCEdCloud Support or refer to the Alias ID Documentation.