Personal Record ReviewU.S. EDITION
OCTOBER 2026

This publication is not affiliated with, sponsored by or operated by the University of Utah. Subject names identify the subjects of the articles, not the publisher.

No university record changes, account services or personal-data intake.

Search
Cookie settings

DOSSIER 01 / PERSONAL INFORMATION AT UTAH

A record is more than one field.

What is shown. What is recorded. Who can see it. Who may receive it.

Read the boundaries before you make a change. An independent guide to personal-record representation and visibility around Utah CIS.

Open the four-layer dossier

What this review is for

For students and former students trying to understand their own record. We interpret public instructions and test the limits of common assumptions. We cannot see your profile, change a record, decide a FERPA request or provide account support.

READING INSTRUMENT / NO PERSONAL DATA

Record Boundary Comparison

Compare a proposed kind of change with the effect you expect. This independent tool uses public instructions, not your record. It cannot approve a change, restrict disclosure or connect to CIS.

The two selections stay in current-page memory. No name, address, contact detail, credential, text entry or upload is requested. No tool network request, cookie or persistent storage is used. Reset clears the result; your browser may restore page state. Printing uses your device and selected printer.

All comparisons, with or without JavaScript

Choose the proposed change below, then read the line for your intended effect. These are the same boundaries used by the interactive comparison.

Chosen-name setting

Change a named-system display
Direct fit, within the published list. Use the chosen first-name process for the documented displays. Some listed contexts show both names. Verify the specific destination. The official list is bounded and does not give a universal completion time. Registrar chosen-name guidance — registrar.utah.edu
Correct the legal name on record
Different route needed. A preferred-name setting is not a documented legal-name correction. Read the official personal-information process and its evidence requirements. Student and employee routes differ. Registrar personal-information process — registrar.utah.edu
Restrict public directory disclosure
Different route needed. A name display choice does not establish a directory restriction. Review Privacy Restrictions separately. A new name on a public display is still a public-display question. Registrar privacy guidance — registrar.utah.edu
Permit a specific person to receive information
Different route needed. Choosing how a name appears does not name a recipient for an education-record disclosure. Review the separate FERPA Consent to Release process for the intended recipient and scope. Registrar consent guidance — registrar.utah.edu

Registrar chosen-name guidance — registrar.utah.edu

Official personal-information change

Change a named-system display
Verify the particular display. A legal-record change and a chosen-name preference are distinct. Do not predict every display from the legal correction alone. Check the source used by the named system and whether a chosen-name preference is relevant. Registrar chosen-name guidance — registrar.utah.edu
Correct the legal name on record
Direct fit, through the official process. The personal-information process is the documented route for a student legal-record change. Use current university instructions and required evidence. This tool cannot verify documents or approve a change. Registrar personal-information process — registrar.utah.edu
Restrict public directory disclosure
Different route needed. Correcting a record does not itself establish a public-directory restriction. Review the restriction process as a separate decision, even if the correction was completed. Registrar privacy guidance — registrar.utah.edu
Permit a specific person to receive information
Different route needed. An accurate legal record does not by itself authorize disclosure to a particular person. Use the official consent process for the recipient and scope, subject to applicable exceptions. Registrar consent guidance — registrar.utah.edu

Registrar personal-information process — registrar.utah.edu

Directory restriction

Change a named-system display
Different question. Restriction concerns public disclosure; it does not select a preferred name. If the goal is a name display, read the chosen-name guidance. Keep any desired restriction as a separate question. Registrar chosen-name guidance — registrar.utah.edu
Correct the legal name on record
Different route needed. A directory restriction does not correct the underlying legal-name record. Use the official personal-information process for a documented correction. Registrar personal-information process — registrar.utah.edu
Restrict public directory disclosure
Direct fit, with limits. The Privacy Restrictions process is the documented route for restricting directory disclosure. It is not erasure or universal secrecy. Ask the Registrar about the scope and any applicable exceptions. Registrar privacy guidance — registrar.utah.edu
Permit a specific person to receive information
Different question. Restricting public information does not itself designate someone to receive protected record information. Ask about the specific recipient and consent route rather than assuming broad directory visibility is required. Registrar consent guidance — registrar.utah.edu

Registrar privacy guidance — registrar.utah.edu

Consent to release

Change a named-system display
Different route needed. Permission to receive information does not select a name for a campus display. Read the chosen-name instructions for the specific system. Registrar chosen-name guidance — registrar.utah.edu
Correct the legal name on record
Different route needed. Consent to disclose is not an instruction to amend the legal record. Use the official personal-information process for a legal-name correction. Registrar personal-information process — registrar.utah.edu
Restrict public directory disclosure
Different question. A release to a specified person is not the same as a public-directory restriction. Review public visibility separately. Ask the Registrar how the chosen permissions apply in your situation. Registrar privacy guidance — registrar.utah.edu
Permit a specific person to receive information
Direct fit, within the official scope. The FERPA consent route concerns disclosure to specified people. Read the actual form. Consent does not itself grant account access or power of attorney; do not share credentials. Registrar consent guidance — registrar.utah.edu

Registrar consent guidance — registrar.utah.edu

THE DOSSIER / READ BY QUESTION

Seven questions, separate answers

7 articles

Sources have edges, too

Public pages were checked October 15, 2026. We identify older navigation labels and interrupted source access rather than pretending to have inspected your account. The editorial method and update record explain the limits.