Comparison
Google gives you sharing permissions and Appointment Schedules. Awase gives you a separate client-facing page with per-calendar privacy, tag filters, and optional booking requests — without changing your Google Calendar visibility settings.
Real-world example
A therapist uses Google Appointment Schedules and accidentally leaves other events visible when a client scrolls. Another client's name — "Follow-up — Sarah M." — appears on a Tuesday block. With Awase, they connect Google read-only, mark the clinical calendar Private on the bookable link (clients see only "Busy"), hide personal events inside Awase, and send one `/share/your-link` URL that never touches Google's public visibility settings.
Native calendar permissions vs filtered share links
| Feature | Awase | Google Calendar sharing |
|---|---|---|
External page without changing Google visibility Keep calendars private in Google; publish a separate Awase URL. | Yes | Requires share settings or making calendars public |
Per-calendar Public / Private on one link Private = busy block only; Public = titles and details shown. | Yes | All-or-nothing share permissions per calendar |
Filter link by calendar tags e.g. only "Client work" calendars on a sales link. | Yes | No equivalent on a single share URL |
View-only and bookable link types Coordination page vs booking request flow. | Yes | Appointment Schedules for booking; separate share for view |
Booking request → host approves → confirmation email Review before confirm; ICS in email. | Yes | Appointment Schedules book directly into Google |
Included free with Google account No additional product. | No | Yes |
Meet links, rooms, Workspace admin policies Native Google infrastructure. | Reads Google events; does not replace Workspace admin | Yes |
Someone needs to book a call. You turn on Appointment Schedules or send "See all event details" because it is fast. The client books — and also sees "Investor dinner" or "Interview — candidate name" two slots away. Busy/free helps, but assistants still cannot run a clean booking operation from Google's share UI alone.
In the dashboard you create a link as View only or Bookable, pick which imported calendars count, filter by tags if you use them, and set each calendar to Public or Private for that link. Private calendars render as busy blocks on the share page. You can also hide individual events on Awase without deleting them in Google. Clients open `/share/your-slug` — no Google account required.
Awase advantage: One URL with rules, instead of resharing Google permissions every time the audience changes.
Three coworkers on Google Workspace coordinating internally with sensible share permissions? You probably do not need another tool. Awase earns its keep at the boundary: paying clients, contractors, and assistants who should not browse your full Google history.
No. Google remains where your events live. Awase imports selected calendars read-only and adds workspace, sharing, and booking layers on top.
Not via API — Awase only has read-only Google access. After you approve a booking, the client gets a confirmation email with ICS. You add it to Google Calendar the same way you would from any email invite.
You could, but most people pick one client-facing front door to avoid conflicting rules. Awase is for when Appointment Schedules cannot express your privacy or assistant workflow.
Use Google Calendar sharing for teammates who already belong in Workspace. Use Awase when outsiders need availability or booking without reading your calendar's diary.
If you maintain a duplicate "public" calendar and copy blocks by hand, you are building manually what Awase automates with filters.
Start freeStep-by-step: bookable link, private calendars, pending approval.
Read the guideThe Public / Private control on share links, explained with examples.
Read the guideBusy blocks vs titles — what clients actually see.
Read the guide