01rule
Setting the condition
We define who gets access at what level to which calendars — one rule can cover many recipients.
Chrono automatically grants and revokes access to the Google Calendars you name, based on a rule you set once — nobody's left with access you forgot about, and nobody new waits on your manual click.
A new team member, assistant or business partner needs access to specific calendars — and every time, someone has to remember to set it up by hand, then revoke it once the collaboration ends.
Chrono automates that granting based on a rule you define once — a new person meeting the condition gets access automatically, with no involvement from you.
The mechanism runs as a script on the source account whose calendars are shared — it needs no separate infrastructure.
A simple mechanism built on the Google Calendar API.
We define who gets access at what level to which calendars — one rule can cover many recipients.
The script checks on a schedule who meets the rule, and grants access without manual intervention.
Once the condition no longer holds, access is revoked just as automatically.
Who gets access to which calendars and at what level.
No infrastructure beyond the Google account itself.
Access always matches the current state of your team or collaboration.
A time trigger checks the rules without your involvement.
You'll know how to add a new rule or change an access level.
Rule changes and small fixes without a fresh setup.
Teams and companies whose calendar access changes regularly — new hires, assistants, project partners — who want to take this off the list of things to remember by hand.
The mechanism has a confirmed track record inside bāAlpha; it's currently in an internal code review phase ahead of full standardization — client rollouts are delivered with that fact stated plainly.
The mechanism is limited to one system (Google Calendar) and one rule — hence the lowest entry price in the bāApps line.
Manual sharing is a one-off action you have to remember to repeat for every new person or calendar. Chrono automates it based on a rule you set once.
Anything supported by the Google Calendar API — from free/busy visibility to full edit rights — agreed individually during setup.
Yes — rules work both ways: granting and revoking access, e.g. when someone stops being part of the team.
As a Google Apps Script on the source account whose calendars are being shared.
The standard setup covers one source account and a rule for a defined group of recipients. More complex scenarios are quoted individually.
Who should get access, and to which calendars — we reply within 2 business days.