Teams
One Awase workspace, owner-connected Google calendars, assistants with permissions — not a shared Google login.
Small teams break scheduling when everyone uses one Google login or pastes screenshots in Slack. One workspace with explicit roles fixes most of it.
Real-world example
A four-person agency founder connects the company Google calendar and a personal hold calendar to Awase. Two ops staff get Manage share links + Approve bookings. Clients use one Bookable link for "Onboarding call (30 min)." Internal events stay Private on the link; approved client bookings show in the workspace dashboard.
Workspace members see the combined dashboard with privacy rules applied — private Google events as busy blocks, approved bookings in full.
Clients see only what the share link allows: Public calendars with details, Private calendars as busy, hidden events omitted entirely.
Owner — connects Google, hides events, manages team, full permissions.
Assistant — invited with toggles for share links, availability, booking approval. Cannot connect Google or delete share links (owner-only delete in current RLS).
Pending bookings surface in the Bookings panel. Whoever has Approve bookings clears the queue. Confirmation emails go to clients automatically on approval — no manual "you're confirmed" email unless you want to add one.
Today the workspace owner connects Google. Team scheduling is centered on that imported set — not a multi-host round-robin.
No. It is a small workspace with assistants and shared operational control — not routing across ten sales reps.
Reading about private availability sharing is one thing. Connecting your Google calendars and sending a test link is the part that usually clicks.
Start free