Sometimes a calendar or video integration that was working fine shows up as disconnected in NeetoCal, even though nobody clicked Disconnect. This article explains why that happens, how NeetoCal tells you, and how to reconnect.
How NeetoCal stays connected
When you connect Google Calendar, Outlook, Zoom, Microsoft Teams or another account, the provider gives NeetoCal a long-lived access key for that account. NeetoCal uses this key in the background to read your calendar, add events, or create meeting links, so you do not have to log in each time. The key expires regularly, and NeetoCal asks the provider for a fresh one automatically.
If the provider refuses to issue a fresh key, NeetoCal can no longer act on your behalf. At that point it marks the integration as disconnected. NeetoCal cannot keep an integration connected once the provider has rejected the key.
Why a provider rejects the key
The provider rejects the key when something changes on the connected account. The exact triggers depend on the provider.
Microsoft (Outlook and Teams) is the strictest. It cancels the key when the user changes their password, changes their MFA setup, when an admin revokes the user's sessions, or when the organization has a sign-in policy that forces everyone to re-authenticate after a set period. Microsoft also cancels a key that has not been used for 90 days.
Google keeps the key through a password change. It cancels the key when the user removes NeetoCal from their Google account's connected apps, or when the key goes unused for six months.
Zoom cancels the key when the user removes NeetoCal from their Zoom account, or when the Zoom account is deactivated.
Because these triggers are tied to the individual account, team members in the same workspace are usually disconnected on different days. If everyone was disconnected at the same moment, contact support.
How NeetoCal tells you
When an integration is disconnected, NeetoCal sends an email to the person who connected it. The subject line starts with "Attention required" and names the integration and workspace. The email contains a Reconnect button that takes you straight to the right page.
A banner also appears at the top of NeetoCal for that person saying the integration has been disconnected, with a link to connect it again.
Workspace admins can also receive these emails for their team members. To turn this on, go to My preferences > Notifications and enable Disconnection of team members integration.
Reconnecting
Click Reconnect in the email or Connect it now in the banner. You can also go to the Host (Self) tab and open the integration's page.
Sign in to the provider account and accept the permissions.
Check that your calendar preferences or video tool are selected as before.
Bookings that were made while the integration was disconnected are still in NeetoCal. Calendar events for that period were not added to your calendar, and video links for that period used the fallback option set on the scheduling link.
Finding out what cancelled the key
NeetoCal only sees that the provider refused the key, not the reason. The reason is recorded on the provider's side.
For Microsoft accounts, your IT admin can open the Microsoft Entra admin center, go to Enterprise applications, open NeetoCal, and check the sign-in logs around the date of the disconnection. Microsoft records a failure code there that names the policy or event that cancelled the key. Granting NeetoCal admin consent in the Azure portal controls what NeetoCal can access, but does not change how long the key lasts, so it will not prevent disconnections on its own.
For Google accounts, the user can check the connected apps list in their Google account to confirm NeetoCal is still listed.