> ## Documentation Index > Fetch the complete documentation index at: https://docs.goguardian.com/llms.txt > Use this file to discover all available pages before exploring further. # Understand How Students Appear in GoGuardian Beacon > Learn where GoGuardian Beacon gets student and guardian data, confirm which students a deployment covers, and troubleshoot a student who is missing from Beacon. GoGuardian Beacon does not have its own student roster. Which students Beacon covers is determined by your Organizational Unit (OU) structure and your Beacon deployments, and the student and guardian details on each alert come from Org Management. This article explains that data flow and how to fix a student who is missing from Beacon. ## Where Beacon Gets Student Data Beacon draws on two sources, both managed outside of Beacon itself: * **Coverage (which students are included):** A Beacon deployment connects Beacon to a set of OUs in your Google domain. Students in a covered OU are included; students outside every deployment are not. OUs are synced in Org Management. See [Create a Deployment](/products/beacon/create-a-deployment). * **Student and guardian details (what appears on an alert):** A student's name, email address, and guardian contact information come from the data in Org Management. Beacon analyzes activity on school-issued devices where the GoGuardian Extensions are installed. See [How Beacon Works](/products/beacon/how-beacon-works). ## Confirm Which Students a Deployment Covers A student is covered only when their OU is part of an active deployment. Confirm all three of the following: * **The student's OU is assigned to a deployment.** Each OU can belong to only one deployment. A student whose OU is in no deployment produces no alerts. * **The specific sub-OU is selected.** Beacon does not automatically include child sub-OUs of a parent OU. Each sub-OU you want covered must be selected individually in the deployment. * **The deployment is active.** A deployment does not send alerts until at least one user is added to its Escalation List. ## Troubleshoot a Missing Student If a student should be covered but isn't appearing in Beacon, work through these causes in order: 1. **OUs are out of date.** Sync your OUs using the sync icon in the top-right corner of Org Management, then recheck the deployment. 2. **The OU or sub-OU isn't in a deployment.** Add the student's exact OU (and any relevant sub-OUs individually) to a deployment. See [Create a Deployment](/products/beacon/create-a-deployment). 3. **The deployment was just changed.** Newly added OUs may take up to 30 minutes to surface alerts. Wait, then recheck. 4. **The device isn't covered.** Beacon analyzes activity on school-issued devices with the GoGuardian Extensions installed. Confirm the extensions are deployed to the student's device. See [Install GoGuardian Extensions](/products/beacon/install-extensions). 5. **The student has had no qualifying activity.** Beacon only generates an alert when its models detect signals of risk. A covered student with no matching activity correctly shows no alerts. ## Update Guardian and Contact Information Beacon sends parent and guardian notifications to the contact information associated with the student in Org Management — it is not entered in Beacon. If a student's guardian contact is missing or incorrect, update it at [manage.goguardian.com/guardians](https://manage.goguardian.com/guardians). For the full workflow, including how Super Counselors request changes, see [Parent and Guardian Notifications](/products/beacon/parent-guardian-notifications). ## Review Sync Timing Expectations * **OU changes:** Sync OUs manually in Org Management; newly added OUs can take up to 30 minutes to surface alerts. * **Guardian contact changes:** Update contacts in Org Management. If a parent notification fails to send, confirm the email address on file is current and free of spelling errors. Assign OUs to a Beacon deployment to define coverage. How Beacon analyzes activity and generates alerts. Configure and maintain guardian contact information. Deploy the extensions Beacon relies on for device coverage.