REL-3379, REL-3302, REL-3363, REL-3274: The Quarantine Nudity feature expands the nudity detection offering and adds a new layer of protection to student safety. Any suspected nude images shared from within the school or by outsiders with anyone in the school will be detected and quarantined so that the intended recipient is not exposed to them. Admins can select the confidence level for which they want images to be quarantined, and even delegate the review of these images to other faculty members.
REL-3164: With this release, partners and ITCs will be able to manage multiple FIDs from a single interface making it easy and convenient for them to manage all their accounts. They would be able to navigate across FIDs, modify rules and settings for each FID individually, and also have all changes logged in the Audit Log to ensure accountability. Note that for Aware-only schools the partner will not be displayed any activity on UI.
REL-3427: Sometimes, schools require large amounts of data to be downloaded for their school's users using a variety of parameters. Until this release, customers were dependant on the Securly support team for such data requirements. Now we have created an API that will allow them to download all such data independently in a secure and dependable manner.
REL-3436: With this release, admins will be able to allow a website for a specific policy even if the TLD for the website is blocked and the website is not in DB16.
REL-3535: This card introduces a new method of indicating flagged, allowed, and blocked activities on the Activities page in the Safety Console. This will help admins identity the different types of activities easily. It also fixes multiple bugs related to the paginated OU issue.
REL-3489: With this we extend the score punishment logic used for grief/self-harm events, to bullying and violence events as well.
REL-3465: This card updates the logic used for matching phrases for AtRisk scores. The new method will work faster and also reduce the number of phrases and their versions that need to be added to the database.
REL-3418: The At Risk score has been extended to violence and bullying events with this release. This is in addition to the self-harm/grief events that students were being scored for.
REL-3582: This increases the number of district-level contacts that can be added for a customer in the on call tool. This will help us accommodate schools that do not follow an OU structure.
REL-3515: This card fixes the problem with some parents not receiving push notifications for flagged activities for their kids.
REL-3531: This card allows OUs with special characters in their names to be saved for a faculty group.
REL-3469: URL blocking was not working as expected for SmartPac users and has been fixed with this card. This means that URLs added to allow/block lists will allow/block websites for users.
REL-3440: It was found that schools with a CIDR range were unable to use the temporary allow feature correctly when using SmartPac. This has been fixed.
REL-3566: The email alert sent for Twitter flagged activities was displaying the URL for twitter incorrectly. This has been fixed.
REL-3559: There was an issue with student login not working correctly when forced login was turned on for the user. This has been fixed.
REL-3571: This card fixes an issue with saving OUs correctly in case of pagination.
REL-3420: It was observed that because of how specific policy name data was stored in ES for SmartPac users, sometimes policies that did not belong to an FID were being displayed on its dashboard. This has been fixed.
REL-3608: This fixes the issue of deleted policies showing up in the policy priority list. Such a policy was displayed to the user as a blank card in the list causing confusion.
REL-3576: It was found that guests on the Guest Network Policy of a school were being displayed the request permission or login button on a blocked page incorrectly. This has been fixed.
REL-3551: This card adds a message for users to download the existing CSV before uploading a new one. This will help ensure that any contacts added manually are also reflected in the CSV and not overwritten if the customer uploads any old CSV.
REL-3483: It was observed that delegated reporting groups users (DA) were incorrectly not receiving self-harm notifications emails when the self-harm notification button was disabled in the Global Settings. DA notifications are governed by settings under the Faculty tab and so emails should be sent or stopped as per that configuration. This issue has been fixed.
REL-3635: This card fixes two issues with the Filter and Aware toggle buttons not working in the on call tab, and changes to OU selection not being saved correctly when modified in the Staff tab.
REL-3589: It was found that domains were not being added to the Allow list for a policy as expected irrespective of whether they were added directly to the list from the policy, or using the Allow button on the Activities page. This issue has been fixed.
REL-3529: This fixes a vulnerability issue with the blocked page that allowed users to inject javascript to the page with malicious intent.
REL-3457: It was found that CSV files saved with the BOM encoded format were not being uploaded correctly during FTP upload. This has been fixed.
REL-3477: This fixes an issue with OUs in the on call tab being unsaved if when any new OUs are saved.
REL-3449: It was found that if a keyword was added to the Global Block list and also falls under a blocked category at the policy level, the system was blocking the keyword as per the policy level setting. It is expected that the Global Block list should be referred to first and keyword blocked for that reason. This has been fixed.
REL-3521: Some schools use both OneDrive and Google Drive. It was found that if OneDrive was onboarded, then channels were not being created for Google Drive as expected. This has been fixed and channels for both are being created successfully.
REL-3520: This fixes an issue with the Safety Console, where if additional OUs are assigned to a contact the contact is not saved correctly and information is also not displayed as expected.
Historical release notes can be found here.
Comments
Article is closed for comments.