Safe Doc Update v1.27.2

[Safe Doc Community]

Hello admins,

Safe Doc v1.27.2 is released. Here are updates: 

1. Added a new BlockUnnicknamedMeeting policy. The policy blocks your students reusing old Google Meet codes. These meet codes in common do not have a nickname and have Quick Access ON, therefore, students could organize their own unmoderated meets. Safe Doc analyzes and blocks these meetings. Learn more about Block Students Joining Old Unsupervised Google Meetings.
2. Fixed an issue of image searching feature bypassed in Slides.
3. Fixed the blocking Email as attachment feature in Google Docs. 
4. Fixed the blocking Add comment icon at the document edge of Google Doc. 

Thank you

--

xFanatical

[Yossi Goldblatt]

Love this update!

There is a glitch in the code - sometimes students get the blocked message even though it is a nicknamed meeting and then when they wait a minute and try again it works. Any ideas?

--
You received this message because you are subscribed to the Google Groups "Safe Doc Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to safedoc-commun...@xfanatical.com.
To view this discussion on the web visit https://groups.google.com/a/xfanatical.com/d/msgid/safedoc-community/cb4a8ba0-b6a8-4b99-9205-d6309717fc56n%40xfanatical.com.

--

Rabbi Yossi Goldblatt

Director of Operations, Yeshiva Bais Yehudah

248-663-8385 (office)

503-381-7260 (cell)

[Safe Doc Community]

Thanks for the feedback, Yossi.

Yes, it could happen. 

By default, Safe Doc checks the meeting nickname in 5 seconds. If the student's device loads the meeting really slow (device CPU busy, network delay etc.), the meeting could be falsely blocked. This exception shall occur rarely, and could be solved by clicking the meeting link again.

But if this exception occurs commonly, we could provide an option to tune the 5 second timing. 

--

Jason Huang

Founder of xFanatical

[Safe Doc Community]

Follow up with the glitch of the BlockUnnicknamedMeeting policy.

A minor update in v1.27.5 added a new policy BlockUnnicknamedMeetingWaitTime to allow you configure the 5 seconds wait time for the BlockUnnicknamedMeeting policy. 

A nicknamed meeting is possible to be falsely blocked by Safe Doc if the meeting couldn't load within 5 seconds due to slow devices or clogged network. Students can click the Reload button in the blocked page to reload the meeting so that the 2nd time could pass.

If this happens a lot, consider extending the 5 seconds waiting time using the BlockUnnicknamedMeetingWaitTime policy. For instance,

"BlockUnnicknamedMeetingWaitTime": {

  "Value": 8

}

--

Jason Huang

Founder of xFanatical

[Yossi Goldblatt]

Thanks, I'll check it out.