Help

Enrollment Cybersecurity Month PowerUp - Delete Form Data & Uploaded Documents

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Enrollment Cybersecurity Month PowerUp - Delete Form Data & Uploaded Documents

Published on ‎10-07-2025 01:05 PM by PowerSchool Team | Updated on ‎10-29-2025 05:13 PM

Watch the recording:

 

Thank you for joining our recent session on Cybersecurity & Data Deletion in PowerSchool Enrollment (25.9.0.0).


If you were unable to attend live, you can now access the recording below to learn how the new functionality allows for deletion of historical form data and uploaded documents.

 

In this session, Patrick provides an overview of how the process works, what data specifically gets deleted, and key implications and considerations for your district.

 



Event has ended
You can no longer attend this event.

Start:
Wed, Oct 29, 2025 09:30 AM PDT
End:
Wed, Oct 29, 2025 10:00 AM PDT
Labels (2)
Attachments
0 Kudos
3 Comments
PatrickW1
PowerSchool Team
Hi all,
 
Thank you for attending today’s Enrollment PowerUp!
 
I wanted to follow up and provide further context regarding the following, as requested:
 
“If document delivery via API to PS SIS has been used, performing these tasks will also make the documents inaccessible in PS SIS.”
 
Basically, since the documents are deleted, they can’t be downloaded anymore.
 
Document Delivery doesn’t physically transfer or replicate the documents to SIS. The documents are retained in Enrollment and the SIS simply receives a reference/ID for each document. When a user accesses the document in SIS, SIS retrieves the document on demand from Enrollment.
 
Therefore, if the documents are deleted on the Enrollment side, they will no longer be accessible on the SIS side.
 
Please let me know if you have any other questions or need further clarification.
 
Best,
 
Patrick

Hi Patrick.  Thanks for the PowerUp on deleting uploaded documents.  On a related subject, is there any documentation regarding the document upload feature in Enrollment that speaks to the secure retention of documents?  In a soon to be released application form, we are going to request a document upload from families and wanted to include in our instructions that they can be assured that these documents are safe and secure.  A note that we will add is that once this application period is complete and we have reviewed their documents, we will delete them utlizing this new available feature.    

PatrickW1
PowerSchool Team

Documents are uploaded to form submissions either by parents or school/district administrators. Uploaded files are transferred to Enrollment servers via HTTPs, where a GUID is assigned and stored in the form submission data, and the blob data corresponding to the file is sent to an Azure Storage Container with the GUID as its identifier. This transfer of blob data to Azure is performed with a Microsoft .NET library using SSL encryption. This Microsoft .NET library uses a private set of credentials to authenticate to the storage account for all upload/download operations. The blob data is encrypted at rest in Azure by Microsoft.

 

No end users are able to access the Azure Storage Containers directly. Only Enrollment Engineering and CloudOps engineers with the appropriate access levels and controls are able to access the Azure Storage Containers for infrastructure implementation, maintenance, and troubleshooting purposes. Enrollment Engineering and CloudOps engineers’ access to the Azure Storage Containers is through PowerSchool’s Azure Active Directory which requires MFA authentication.

 

Documents can be downloaded by school/district administrators. Documents are grouped by type/purpose within each form. Access to document types is controlled at a permission profile level and permission profiles are assigned to school/district administrators on a form by form basis, allowing districts to control what users have access to what document types per form. IDOR protections applied within the Enrollment application prevent unauthorized access to the backend document retrieval calls. Downloaded files are retrieved from Azure via the same Microsoft .NET library using SSL encryption and are sent directly to the requesting client browser. The downloaded files sent to the browser are not cached.