Week 03 · lesson
DigitalLearn Lab: Google Calendar
Open the official DigitalLearn Google Calendar course materials and complete the learner activity available there using your school-managed environment.
Calendar is easy to underestimate because an event looks simple. A useful event actually coordinates several pieces of information: time, title, attendees, location or meeting context, description, reminders, and linked resources.
Preserve the source activity
Follow the DigitalLearn Calendar learner activity as published where it matches the school environment. If a source instruction expects a feature disabled by your district, record the restriction rather than trying to bypass it.
Add the link-permission test
Create or use a course-safe practice event. Add a link to a harmless Drive agenda or teacher-provided sample document.
Now stop and inspect two different access systems:
CALENDAR EVENT ACCESS
↓
WHO RECEIVES / SEES EVENT?
DRIVE RESOURCE ACCESS
↓
WHO CAN OPEN / COMMENT / EDIT FILE?
An attendee can receive the event and still be blocked from the agenda. The event invitation does not automatically repair the file permission.
Record the intended relationship:
| Resource | Intended audience | Required action | Verified role/access |
|---|---|---|---|
| Calendar event | project team | view event details | |
| Agenda Doc | project team | comment on agenda |
Time is evidence too
Check the event's start time, end time, and time zone/context if relevant. A meeting that is perfectly written but scheduled for the wrong date is still a failed workflow.
If you use a reminder, choose a timing that supports the task. “More reminders” is not automatically better.
Interface drift record
If the current Calendar screen differs from DigitalLearn's source material, record one difference and the current verified path that accomplishes the same classroom-safe result.
Lab exit
Your evidence contains:
- completed DigitalLearn Calendar activity;
- one event state record with date/time and intended audience;
- one linked-resource permission check;
- one interface/policy difference if present;
- one sentence explaining why an event invitation and Drive permission are separate tests.
Source credit: DigitalLearn.org — Google Calendar, CC BY-NC-SA 4.0 unless an individual item states otherwise. Robotnix adds the connected-workflow evidence above.