Give your whole program seamless meeting scheduling from day one. Calendar Connect for Organizations lets your organization authorize calendar access once, at the domain level, so participants don't need to connect their calendars individually and can schedule meetings from the moment they join.

Who is this for?

Calendar Connect for Organizations suits any program where participants share an email domain and you or your IT team control that domain's permissions — typically a corporate organization, government body, or university.

For example:

• georgia@companyname.com
• sally@companyname.com
• jordan@companyname.com

It works with Google Workspace and Microsoft 365.

Participants whose email address sits outside your domain — external mentors, alumni, anyone on a personal address — aren't covered by your organization's authorization, and can't be. They can connect their own calendar individually instead, which takes them under a minute.

What does it give participants?

• Availability between mentoring partners, so a time that suits everyone can be found without back-and-forth
• Meetings added to calendars automatically when they're scheduled in Mentorloop, with invitations sent by your own calendar system
• Changes kept in step — if a meeting is rescheduled or canceled, calendars and Mentorloop stay aligned
• Their preferred meeting tools (Zoom, Microsoft Teams, phone, video calls) still work when scheduling

For you, that means more of your program's meetings are actually captured, and your reporting reflects what really happened.

What are we asking your IT team to approve?

One sentence, which is also what your administrator sees on screen:

Allows Mentorloop's scheduling service to see when people in your organisation are busy or free, and to create and manage calendar events for meetings booked through Mentorloop.

What it does not allow:

• Reading event titles, descriptions, locations, attendees, or attachments. Mentorloop doesn't request the permission that would make this possible.
• Reading, changing, or deleting any event other than the mentoring meetings created through Mentorloop.
• Any access to email, files, chat, or anything else.
• Keeping a copy of anyone's calendar. Availability is read at the moment it's needed and then discarded.

If you'd prefer to start with availability checking only — no meetings written to calendars — tell your Customer Success Manager before they send your approval link. You can enable meeting creation later as a separate decision.

How do we set it up?

1. Talk to your Customer Success Manager. Let them know you'd like Calendar Connect for Organizations, which email domains your participants use, and whether you're on Google Workspace or Microsoft 365.

2. We send you an approval link. Your CSM will send a link, and — for Google Workspace — a Client ID and list of permissions for your administrator to check against what appears on screen.

3. Your administrator approves it. They'll need super administrator access (Google Workspace) or the ability to grant tenant-wide admin consent (Microsoft 365). It takes a couple of minutes.

Full step-by-step instructions are in Calendar Connect for Organizations — Guide for IT Administrators, which is written for them rather than for you. Send them that link along with the approval link.

4. Tell us when it's done. There's no notification from Google or Microsoft when an approval completes, so we don't assume. Your CSM runs a quick check that reads availability for one address in your domain. If it works, you're live. If it doesn't, we can see exactly why and sort it out.

Until that check passes, nothing in your organization is being read.

What do participants need to do?

Nothing. Once your organization is connected, participants see their calendar is already set up:

Your calendar is connected by your organisation — there's nothing to set up.

They can still set their availability rules — the weekly hours they're happy to be booked in — which we encourage, because it stops meetings landing at 7am on a Monday. That's in Account settings → Integrations, and it's covered in Calendar Connect: Connect your calendar and set your availability.

A participant who'd rather use a different calendar — a personal one, say — can connect their own, and it will be used instead of the organization connection. That's deliberate: someone's own choice about their own calendar takes precedence.

Can we turn it off?

Yes, at any time, in your own console — you don't need to go through us, and access stops immediately.

• Google Workspace: Admin console → Security → Access and data control → API controls → Domain-wide delegation → remove the Mentorloop Client ID.
• Microsoft 365: Entra admin center → Enterprise applications → the Mentorloop application → remove it or revoke its consent.

Two things worth knowing:

• Meetings already in people's calendars stay there. They belong to the people in them.
• Individual connections aren't affected. If a participant connected their own calendar, that's their own grant. It isn't covered by your organization's authorization and doesn't end with it.

Where can I read more?

• Calendar Connect for Organizations — Guide for IT Administrators — the step-by-step for whoever approves it, including the exact permissions requested
• Calendar Connect: How your calendar data is handled — what's read, what's stored, where it's processed, and for how long
• Mentorloop Calendar Connect — Security and Data Handling — the full technical document for a security review. Ask your CSM