The calendar builds itself from the bookings you already loaded

No. The Tripwise calendar lives inside Tripwise: it does not produce .ics files, it cannot be subscribed to from Google Calendar, Outlook or Apple Calendar, and it does not publish a shareable link for anyone outside. It is a working screen for the team, not a calendar that syncs to your devices.

Not the booking ones. Departures, returns, check-ins, check-outs, transfers, insurance validity and expiry dates appear on their own from what you already loaded on each booking, and if you fix a date the event moves with it. Separately you can create your own events, which are entered by hand, with a title, description, a time or all-day, and the whole agency sees them.

It depends what. There is a push and email warning when a trip is coming up, fourteen, seven, three and one day before, to the booking's seller and approver; and when a travelling passenger's document is about to expire, sixty, thirty, fifteen and seven days before, to the seller. Allotment and accommodation expiry dates, by contrast, are visual: you see them on the calendar and under Upcoming expirations on Home, but they do not trigger a notification.

Yes. The calendar shows the whole agency's operation, not just your own bookings, which is exactly what lets you see who departs tomorrow or what expires this week regardless of who loaded it. Editing and deleting a booking, on the other hand, is limited to your own.

No. Your own event has a title, a description, dates and an all-day option, and nothing else. There is no recurrence, no guests, no assigned owner, no colour or category, no file attachments and no dragging it to another day. There are no private events either: whatever you add, the rest of the agency sees.