Skip to app details
Back to app library
APPNEURAL APP FAMILYWorkspace

Calendar

Who is where, and when everyone is free

Keep personal and team calendars, invite people inside and outside the team, and find a time that suits everyone.

01 / OVERVIEW

See where it fits in your day.

Each person's own calendar is made on first use and is private; more calendars can be personal or team calendars shared with chosen people or the whole team as free/busy only, all details, or make changes. Views are day, week, month, a 30-day agenda and a team view of chosen people side by side, in each person's zone (Asia/Kolkata by default) with working hours shaded; events are created, moved and resized by dragging. Events carry their own zone, all-day or multi-day times, a place, a video link (a Meetings room when Meetings is connected), notes, guests from the team or any email, up to five email or in-app reminders, links as attachments, busy-only details and free or busy. Recurrence is the app's own RFC 5545 engine (daily, weekly on chosen days, monthly by date or by nth or last weekday, yearly, interval, count, until) with DST-safe wall times, and edits apply to this event, this and following, or all. Invitations go by email with an invite.ics (METHOD:REQUEST) and each guest's /i/<token> RSVP link; updates and cancellations follow, and answers notify the organizer. A 5-minute cron sends each reminder once and the opt-in morning agenda. Each calendar can have a private /ics/<token>.ics subscribe feed for Google, Apple or Outlook; .ics files import and update by UID, and domain owners can mirror ICS URLs hourly. Find a time shows each person's busy blocks and the common free times inside working hours. Optional read-only overlays show approved leave (Leave), bookings (Meetings and Timeslots) and renewal dates (Renewals) through service bindings and API keys pasted in Settings. Version-checked edits, GET and POST /api/v1/events and GET /api/v1/freebusy, webhooks event.created, event.updated, event.cancelled and event.rsvp, a workspace feed, and Claude for quick add from a sentence and the agenda summary.

A LOOK INSIDEExample layout · sample content
This week
MON9
Sample planWeekly review
TUE10
WED11
Sample planClient call
THU12
Sample planTeam lunch
FRI13
Illustrative weekly layout
02 / CAPABILITIES

Built around the work you do.

What Calendar does for you.

01

Views

Day, week, month, agenda and a team view side by side, in India time by default or each person's own zone.

02

Events

Repeating events with exceptions, guests, email and in-app reminders, video links, and busy-only details for others.

03

Invite and connect

Invitations with an .ics file and an RSVP link, a subscribe feed for Google, Apple or Outlook, and .ics import.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Calendar. What you can do depends on your access in the app.

01

Open your calendar

Your own calendar is made the first time you open the app; add team calendars when you need them.

02

Plan

Drag to create, move or resize events, and use Find a time for several people.

03

Invite

Add guests by name or email; they answer from the invitation's RSVP link.

YOUR NEXT MOVE

Make Calendar part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each person's own calendar is made on first use and is private; more calendars can be personal or team calendars shared with chosen people or the whole team as free/busy only, all details, or make changes. Views are day, week, month, a 30-day agenda and a team view of chosen people side by side, in each person's zone (Asia/Kolkata by default) with working hours shaded; events are created, moved and resized by dragging. Events carry their own zone, all-day or multi-day times, a place, a video link (a Meetings room when Meetings is connected), notes, guests from the team or any email, up to five email or in-app reminders, links as attachments, busy-only details and free or busy. Recurrence is the app's own RFC 5545 engine (daily, weekly on chosen days, monthly by date or by nth or last weekday, yearly, interval, count, until) with DST-safe wall times, and edits apply to this event, this and following, or all. Invitations go by email with an invite.ics (METHOD:REQUEST) and each guest's /i/<token> RSVP link; updates and cancellations follow, and answers notify the organizer. A 5-minute cron sends each reminder once and the opt-in morning agenda. Each calendar can have a private /ics/<token>.ics subscribe feed for Google, Apple or Outlook; .ics files import and update by UID, and domain owners can mirror ICS URLs hourly. Find a time shows each person's busy blocks and the common free times inside working hours. Optional read-only overlays show approved leave (Leave), bookings (Meetings and Timeslots) and renewal dates (Renewals) through service bindings and API keys pasted in Settings. Version-checked edits, GET and POST /api/v1/events and GET /api/v1/freebusy, webhooks event.created, event.updated, event.cancelled and event.rsvp, a workspace feed, and Claude for quick add from a sentence and the agenda summary.

Personal and team calendars: events, recurring events, invitations with RSVP links, reminders, ICS subscribe feeds and import, free/busy for finding a time, and read-only overlays of leave and bookings.

Booking pages for clients belong to Timeslots and Meetings; scheduled jobs belong to Scheduling; leave belongs to Leave.

Priority
P2
Portfolio
Workspace
Capability
Workspace
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:13
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

calendar schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

calendar.appneurox.com DEPLOYED

calendar.appneurox.com

Worker
calendar-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:13
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/calendar-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app