Open A3.Calendar

Ecosystem

The Calendar is not another app next to the products, it is a layer beneath them. Here is where the boundary of responsibility runs and what follows from it.

Where the boundary runs

The source product owns the fact

What kind of leave this is, whose hearing that is, for which case and on what grounds. The product creates the fact, changes it and answers for its meaning.

The Calendar owns the schedule

When it happens, whether it repeats, which zone it started in, who takes part and who to remind. Products do not write this logic themselves.

That is why a product event is not edited in the Calendar grid: there is one path to an edit, a link back to the product card. Otherwise the projection would drift from the source of truth.

Products in the integration registry

The registry stores registered products and the permissions granted to them. A product key authorizes writing events, its permissions limit it.

Two directions with A3.Meet

The initiative to create a room can come from either side, so the directions are independent.

  • From A3.Meet into the Calendar

    A3.Meet writes the event through the contract and fills in the room link right away. The Calendar shows the meeting together with the rest of the schedule.

  • From the Calendar into A3.Meet

    A person creates an event with a video flag, the Calendar calls A3.Meet to provision a room and saves the resulting link on the same event.

Integrations with external video services and parsing mail for bookings are out of scope: the Calendar has no access to personal mail outside A3.Mail and will not get one.

A widget instead of your own grid

A product that needs to show a schedule inside its own interface embeds a widget over the event and availability queries. There is no need to render a grid of days.

  • The frame is embedded into the interface of the consuming product
  • Data comes from the same contract endpoints as the web app
  • The product server receives a short-lived widget token; the user session never enters the frame
  • The product call key never reaches the frontend

What is taken from the suite rather than written again

  • A3.ID

    Sign-in, domains, companies and the subscription. Departments, working hours and calendar rights are set up in the calendar itself.

  • Public holidays

    Holidays and shifted days of five countries come from the shared library: there is no holiday table here.

  • Integration registry

    The model of registered products and their permissions repeats the one used by the other infrastructure products.

  • Mail and notifications

    Invitations and reminders go out through the same delivery mechanism as the rest of the ecosystem mail.

Works together with

Connect your product

Registering a product, granting a scope and making the first event write call are described in the contract documentation.

API documentation