meetergomeetergo Help

Connecting Exchange with Calendar Permission

Connect meetergo to Exchange with an account that only has rights on the calendar. No access to emails, no impersonation role.

Updated on October 5, 2026

With this connection type, meetergo signs in with a separate account that only has rights on one user's calendar. meetergo reads availability from that calendar and saves bookings directly into it. The account has no access to emails, contacts or any other folder of the mailbox.

This is the recommended setup for organizations that do not want meetergo to use their users' personal credentials.

How it differs from a service account with impersonation

Calendar permissionService account with impersonation
Rights in ExchangeEditor on one calendarApplicationImpersonation role
Access to emailsNoYes, the whole mailbox
Invitations"Account on behalf of user"as the user

You can create one account per user, or one shared account with rights on several calendars. Both work the same way.

Step 1: Create the account

Create a regular account in Exchange that only meetergo uses, for example meetergo-calendar@yourcompany.com. Give it a strong password that does not expire.

Step 2: Grant rights on the calendar

The account needs Editor rights on the user's calendar. To send invitations to attendees, it also needs Send on Behalf.

Run in the Exchange Management Shell:

$owner = "thomas@yourcompany.com"
$account = "meetergo-calendar@yourcompany.com"

# Find the user's calendar folder (its name depends on the mailbox language)
$calendar = $owner + ":\" + (Get-MailboxFolderStatistics -Identity $owner -FolderScope Calendar |
  Where-Object FolderType -eq "Calendar").Name

Add-MailboxFolderPermission -Identity $calendar -User $account -AccessRights Editor
Set-Mailbox -Identity $owner -GrantSendOnBehalfTo @{Add = $account}

If the account already has a different permission on the calendar, use Set-MailboxFolderPermission instead of Add-MailboxFolderPermission.

Alternatively, the user can add the account in Outlook as a delegate with Editor rights on the calendar. That grants both rights at once.

Several users at once

If one shared account serves several calendars, repeat the commands for each user:

$account = "meetergo-calendar@yourcompany.com"
$owners = "thomas@yourcompany.com", "anna@yourcompany.com"

foreach ($owner in $owners) {
  $calendar = $owner + ":\" + (Get-MailboxFolderStatistics -Identity $owner -FolderScope Calendar |
    Where-Object FolderType -eq "Calendar").Name
  Add-MailboxFolderPermission -Identity $calendar -User $account -AccessRights Editor
  Set-Mailbox -Identity $owner -GrantSendOnBehalfTo @{Add = $account}
}

Step 3: Connect in meetergo

  1. In meetergo, open Integrations and choose Exchange.
  2. Click Add Connection.
  3. Under How does meetergo sign in?, choose Account with calendar permission.
  4. Fill in the form:
    • Email of the calendar: the email address of the user whose calendar you connect.
    • Password of the account with access: the password of the account from step 1.
    • Exchange server: the EWS URL, for example https://mail.yourcompany.com/ews/exchange.asmx.
    • Domain: only needed if your setup requires a NetBIOS domain in front of the username.
    • Username of the account with access: for example meetergo-calendar@yourcompany.com or DOMAIN\meetergo-calendar.
  5. Click Connect.

While connecting, meetergo checks that the account can read and edit the calendar. If rights are missing, meetergo tells you which ones.

Troubleshooting

  • "The account lacks create, modify, delete permission": the account only has read rights. Grant Editor as in step 2.
  • Bookings are not saved: usually Send on Behalf is missing. Without it, Exchange refuses to send the invitation.
  • The connection fails right away: check that the EWS endpoint is reachable and that the account is allowed to use EWS.
  • Appointments land in the account's calendar instead of the user's: the connection was created with Own account. Disconnect it and connect again with Account with calendar permission.

For the impersonation alternative, see Using an Exchange Service Account for Your Connection.

Was this article helpful?

Let us know if this article answered your questions.