You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some students on our courses that have enabled outlook calendar sync on their accounts.
We also the the attendance module for adding attendance registers which get added to the course calendar and synced down to whatever students have sync enabled. The population of attendance sessions is done by a central team via a bulk import process.
It appears, as the \core\event\calendar_event_created event happens and is associated with whoever the central admin was to do this import, they then get added as the "organiser" within the students calendar, thus adding a calendar event to the central admin's calendar for every course session where a student has calendar sync enabled.
As they are not involved in the teaching process at all, this is an undesirable effect.
Is there a way around this? Or is this potentially a misconfiguration of various plugins on our part?
The text was updated successfully, but these errors were encountered:
We have some students on our courses that have enabled outlook calendar sync on their accounts.
We also the the attendance module for adding attendance registers which get added to the course calendar and synced down to whatever students have sync enabled. The population of attendance sessions is done by a central team via a bulk import process.
It appears, as the \core\event\calendar_event_created event happens and is associated with whoever the central admin was to do this import, they then get added as the "organiser" within the students calendar, thus adding a calendar event to the central admin's calendar for every course session where a student has calendar sync enabled.
As they are not involved in the teaching process at all, this is an undesirable effect.
Is there a way around this? Or is this potentially a misconfiguration of various plugins on our part?
The text was updated successfully, but these errors were encountered: