Six useful guides.
No content maze.
Start with the guide that matches your problem. Each page explains what you can try, what an organization can block, and when you need help from IT.
- Official sources linked
- Current product behavior checked
- Limits stated plainly
Published by manyCalendars.
The manyCalendars editorial team maintains these six guides. Drafting tools may help with structure or copy editing. Product claims, links, and limits are checked against current behavior and primary provider documentation before publication.
Start with the problem you have.
These three guides cover blocked accounts, calendars from different companies, and the ways manyCalendars can read a calendar.
One calendar view when admin approval is off the table
The legitimate options, the policies that can stop each one, and where a browser-session bridge fits.
How to view work calendars from different companies
A decision tree for client laptops, separate tenants, browser profiles, sharing links, APIs, and blocked connections.
How manyCalendars reads calendars
A direct explanation of feeds, chosen browser tabs, structured reading, fallbacks, local storage, and optional web access.
Three specific questions.
Use these when the issue is double booking, extension permissions, or deciding where calendar details should live.
A practical anti-double-booking system for multiple clients
What can work today, what requires write access, and where a read-only unified view helps without making promises it cannot keep.
Browser extension permissions for calendar readers, in plain English
Why a bridge needs page access, what it should never collect silently, and which controls users should expect.
What “availability only” should mean
Busy windows can still reveal patterns. A useful privacy model makes every field and every destination explicit.
Get an email when a Free or paid spot opens.
Current member capacity is full. Join the waitlist and we will email you when the next Free or paid spot opens.