<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Protecting Accounts for young learners in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141149#M4011</link>
    <description>&lt;P&gt;This is related to this post:&amp;nbsp;&lt;A href="https://www.googleforeducommunity.com/t5/Discussion/Context-Aware-Access-to-User-Account/td-p/140696" target="_blank" rel="noopener"&gt;https://www.googleforeducommunity.com/t5/Discussion/Context-Aware-Access-to-User-Account/td-p/140696&lt;/A&gt;&lt;/P&gt;&lt;P&gt;We're a K12 school, and I'm keen to learn how others protect accounts for the early learners (Prep to Year 3 mostly). I had been hoping to restrict access to certain accounts using Context Aware Access (see above article) but that isn't possible using CCA.&lt;/P&gt;&lt;P&gt;We're a 1:1 school (each student has their own chromebook provided and managed by the school), and each student has their own account. For later years (Year 4 and up) students have a complex password (we reset all passwords each year), but the younger years have lots of trouble with complex passwords.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had hoped to restrict access to those accounts to our Campus (based on our IP range), but considering that's not possible, I'm keen to hear what others are doing to balance security and convenience for those younger years?&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2025 22:28:15 GMT</pubDate>
    <dc:creator>Olger</dc:creator>
    <dc:date>2025-04-03T22:28:15Z</dc:date>
    <item>
      <title>Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141149#M4011</link>
      <description>&lt;P&gt;This is related to this post:&amp;nbsp;&lt;A href="https://www.googleforeducommunity.com/t5/Discussion/Context-Aware-Access-to-User-Account/td-p/140696" target="_blank" rel="noopener"&gt;https://www.googleforeducommunity.com/t5/Discussion/Context-Aware-Access-to-User-Account/td-p/140696&lt;/A&gt;&lt;/P&gt;&lt;P&gt;We're a K12 school, and I'm keen to learn how others protect accounts for the early learners (Prep to Year 3 mostly). I had been hoping to restrict access to certain accounts using Context Aware Access (see above article) but that isn't possible using CCA.&lt;/P&gt;&lt;P&gt;We're a 1:1 school (each student has their own chromebook provided and managed by the school), and each student has their own account. For later years (Year 4 and up) students have a complex password (we reset all passwords each year), but the younger years have lots of trouble with complex passwords.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had hoped to restrict access to those accounts to our Campus (based on our IP range), but considering that's not possible, I'm keen to hear what others are doing to balance security and convenience for those younger years?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 22:28:15 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141149#M4011</guid>
      <dc:creator>Olger</dc:creator>
      <dc:date>2025-04-03T22:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141406#M4013</link>
      <description>&lt;P&gt;We use Clever badges for PK-2nd, toward the end of 2nd grade they start learning how to log in with a password.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 13:05:53 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141406#M4013</guid>
      <dc:creator>panderson</dc:creator>
      <dc:date>2025-04-04T13:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141407#M4014</link>
      <description>&lt;P&gt;+1 for Clever - we use same setup as panderson.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 13:14:18 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141407#M4014</guid>
      <dc:creator>Scott_Kovis</dc:creator>
      <dc:date>2025-04-04T13:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141408#M4015</link>
      <description>&lt;P&gt;I will agree with the Clever approach or even Classlink. We use badges with our K-2 students as well. Our 3rd graders follow the same password process as&amp;nbsp;&lt;a href="https://www.googleforeducommunity.com/t5/user/viewprofilepage/user-id/121"&gt;@Scott_Kovis&lt;/a&gt;&amp;nbsp;&lt;a href="https://www.googleforeducommunity.com/t5/user/viewprofilepage/user-id/584"&gt;@panderson&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 13:20:16 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141408#M4015</guid>
      <dc:creator>Dean_Mantz</dc:creator>
      <dc:date>2025-04-04T13:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141537#M4021</link>
      <description>&lt;P&gt;Clever Badges, interesting. Can I use those just for logging in? I had a look at the clever website, but wasn't clear on that. We do everything in Google Workspace, all apps are deployed and controlled through there, and I'd want students to log in through Clever, but then come back to their normal chrome desktop.&lt;/P&gt;&lt;P&gt;Aside from setting up the younger grades in Clever, is all that is required an extension to make the chromebook log in to Clever? I do like that approach.&lt;/P&gt;&lt;P&gt;We don't need any of the SIS integration or other features. Can Clever sync from an API? Or alternatively, can it sync data from a Google Sheet? I import hourly all students from our SIS into a Google Sheet for other purposes, and could use that for Clever too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Apr 2025 09:22:27 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141537#M4021</guid>
      <dc:creator>Olger</dc:creator>
      <dc:date>2025-04-05T09:22:27Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141540#M4022</link>
      <description>&lt;P&gt;Depending on your SIS you can either sync through API or just use data uploads via SFTP.&lt;/P&gt;&lt;P&gt;Once users have been synced and you have turned on badges for the schools/grades you want, you will set your chromebooks for that building's ou to use Clever SAML SSO.&amp;nbsp; There is a setup wizard that will walk you through the steps, it is very straightforward.&lt;/P&gt;&lt;P&gt;Although you say you do not need any other features, if you are setting up Clever I'd strongly recommend looking into rostering your various other third party apps through it.&amp;nbsp; I cannot stress enough how much of a time saver it is, and how nice it is to have all of our rostering done through a single pane of glass.&amp;nbsp; You pick the app you're using, tell it what grades, buildings, or teachers to share it with, and you're done.&amp;nbsp; All of the school accounts you need for that website are now automatically syncing and updating whenever changes are made from your Clever data uploads/syncs.&amp;nbsp; Even for our students who do not use badge login, we set their homepage to the Clever portal so they get a full menu of our apps when they log in.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 14:07:39 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141540#M4022</guid>
      <dc:creator>Scott</dc:creator>
      <dc:date>2025-04-07T14:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting Accounts for young learners</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141625#M4027</link>
      <description>&lt;P&gt;Yes, Clever can be updated through a CSC file.&amp;nbsp; A couple of other things, if you have the paid version of Workspace and use Google Classroom, with the SIS integration you can have it create classrooms for all your teachers. The do still have everything pretty much the same, except you an use a Clever Portal and you can set up a lot of the programs to use Clever authentication and save the hassle of having to roster the program through CSV files.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 13:17:04 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Protecting-Accounts-for-young-learners/m-p/141625#M4027</guid>
      <dc:creator>panderson</dc:creator>
      <dc:date>2025-04-07T13:17:04Z</dc:date>
    </item>
  </channel>
</rss>

