What a team can and cannot see about your calendar

A team never sees your calendars, your events, your connections or your sync rules. That holds for Managed and Sponsored members alike, and for the Owner and Admins. Being on a team gives the people who run it a way to manage membership and billing. It does not give them a way into anyone's calendar.

This page is exact about the other side too: what the people who run a team do see. For the bigger picture, start with How teams work.

What nobody on the team side sees

• Which calendars a member has connected, or whose they are
• The events on them, or any copy of an event
• Which calendar syncs to which, or the rules on a sync
• Who someone's secondaries are
• What a member's own settings say

Where the team's tools need to show an effect on a person, they show names and counts only. A policy preview, for example, says how many connections would be affected and for whom, never which calendar goes where.

What the Owner and Admins see

What someone sees depends on their abilities, so this is what the Owner and Admins see by default. A team can narrow it with groups. A plain member sees the team's name, who runs it and where it stands (forming, on its trial, paid or lapsed), and nothing about who else is on it.

The member list. Each person's name, sign-in address, the date they joined, their role, whether their account is Managed or Sponsored, and the groups they are in. This needs the ability to see members and seats.

Invitations. Who was invited by email or by list, with the status (sent, opened, not interested or expired). People invited by a company domain are only counted: the team sees "N waiting" and never who they are until someone accepts.

Join requests. The name and address of anyone who asked to join through a link.

Domains. The domains the team has added, how each was verified, and, for a domain verified by DNS record, how many people were brought in at the last check (kept for a week).

The team's standing. Everyone on the team sees where it stands: forming (how many of the five people needed are using GetCalendario), on its trial (when it ends), paid or lapsed. Only someone who can manage billing, the Owner by default, also sees the number of seats billed once the team is paid.

The activity log. A record of what happened on the team and who did it: invitations, approvals, joins, people leaving or being removed, policy and group changes, and changes of Owner. Reading it needs the ability to see the activity log. It records that a member deleted their own account without naming them.

Policy previews. Names and counts, as above.

Whoever can remove or release people also sees departure reports for the last 60 days.

What a departure report contains

When a Managed member is removed or released, GetCalendario takes back off the calendars what it wrote there. The report says how that went, in one sentence, such as "4 calendars cleaned; 1 couldn't be reached". It contains:

• The person's name, whether they were removed or released, and a one-sentence summary (the team page shows the date next to it)
• How many calendars were cleaned, and how many could not be reached, with the reason (for example, that GetCalendario's access had been revoked)
• Whether work is still under way
• For a release, any shared Microsoft calendars that could not be checked, because Microsoft does not say whose they are

It never lists calendar names, events or the person's other accounts, and it does not say "all clean" when something was not. The Owner gets it by email, and so does whoever pressed the button if that was someone else. It also appears next to the departure on the team page.

What stays private

A member's own sync rules, connections and calendars. Their personal settings. Which of their accounts are secondary. A Sponsored member's account, which is theirs, is never frozen or cleaned out by the team.

One thing is shared with the team by design: a Managed account belongs to the team, so the team can remove or release it. That affects what GetCalendario copied, not what the team can read.

Related

Team members: Owner, Admin, Managed and Sponsored, Team groups and permissions, Team policies and Leaving, removing and releasing people from a team.