The Student Mart holds admissions, enrollment, and academic-performance data, and access is granted through Federated Authorization so that each person reaches only the data their role requires. This article covers what the Student Mart contains, how to submit an access request, how requests are approved, and who is involved at each step. For the full request-and-approval walkthrough that spans every Federated Authorization system, see Getting Started with the Federated Authorization (FedAuth) Community.
About the Student Mart
The Student Mart is part of the University Data Warehouse and contains information on admissions, enrollment, class enrollment and schedules, the course catalog, tuition, financial aid, freshman retention, and graduation. Most data refreshes daily except on Sundays; term-census, monthly, and in some cases daily snapshots are also available. The data can be reached through Tableau, direct SQL query, and other reporting tools.
Standard access comes first.
You must hold Student Mart access to request Restricted data — fields such as demographics, performance indicators, financial aid information, personal identifiers, and access to additional schools' data. You can request both at the same time, or add Restricted data to an existing authorization later.
Before You Begin
Have the following ready before you open a request:
- The username of the requestee — the person who will use the access.
- The specific data or reports needed, plus a short business justification. Request only the access the role requires.
- The requestee's Security Contact, since Student Mart requests are submitted by, or routed through, the requestee's Security Contact.
- Readiness to accept the User Agreement if a Security Contact is submitting on the requestee's behalf.
How to Request Access
- Log in to the Federated Authorization Community.
- Select the Student Mart tile.
- Complete every required field, including the requestee, the access needed, and your business justification. To request Restricted data, select the corresponding Restricted options on the form.
- If a Security Contact is submitting the request, accept the User Agreement. Select Submit.
- Your request routes automatically for the required approvals. You will receive email messages as it moves through each stage.
- Once every approval is complete, Pitt Digital Analytics implements the access and sends a confirmation message.
For a video walkthrough, see the Student Mart (ST) Request training video.
Log In to the FedAuth Community →
How Requests Are Approved
Student Mart requests move through a fixed sequence of approvers. Requests that include Restricted data add a Data Steward and/or Privacy Officer step.
How Student Mart access requests are routed for approval, by access level
| Stage |
Standard Student Mart Access |
Restricted Data Access |
| Initiated by |
User or Security Contact |
User or Security Contact |
| Before submission |
User Agreement (if submitted by Security Contact); supervisor is notified |
User Agreement (if submitted by Security Contact); supervisor is notified |
| First approval |
Security Contact for the requestee's RC |
Security Contact for the requestee's RC |
| Second approval |
Not required |
Data Steward |
| Third approval |
Not required |
Privacy Officer |
| Implementation |
Pitt Digital Analytics |
Pitt Digital Analytics |
Who's Who in the Request
The people and teams involved in a Student Mart access request
| Role |
Responsibility |
| Requestee |
The person who will use the access. |
| Security Contact |
Submits or approves requests for their Responsibility Center and confirms the access requested is appropriate. View the Student Information System Security Contacts list. |
| University Data Steward and/or Privacy Officer |
Provides the additional approval required whenever Restricted data is requested. |
| Pitt Digital Analytics |
Implements the access once all approvals are complete. |
Troubleshooting
I received an error about a problem with the requestee data.
The message ends with Issue with the requestee data. Please contact support. This usually means the requestee's username is not a primary account. If the account was recently converted to primary, wait up to 48 hours for the change to propagate, then resubmit.
I need a status update on a pending request.
Status visibility is limited to approvers. Contact your Security Contact first. If they cannot help, contact the Technology Help Desk at 412-624-HELP (4357).