TEAM SCHEDULING & CONTEXT
Plan time with the people and work it belongs to.
Create internal events, keep their discussions nearby and inspect supported appointments and business deadlines through the calendar.
Bring a meeting’s purpose closer to its time
The team needs more than a free square in a calendar. They need to know who is involved, what the meeting concerns and where its preparation lives. Tsumira gives internal events their own records, with dates, participants and optional customer or project context. The business calendar then provides a broader way to inspect supported commitments without making every underlying workflow the same kind of event.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Team events
Create a timed or all-day team event with participants, location, notes and optional customer or project context.
Meeting participants
Choose active team members for an internal event and keep participation separate from the right to change the meeting or post in its conversation.
Business calendar
Move between month, week and day, filter available business sources and open the record behind a meeting, booking or deadline.
Meeting conversations
Discuss preparation and follow-up in an internal event thread, with messages, mentions and attachments checked against the event’s own access.
Calendar subscriptions
Create a personal subscription link, keep control over its validity and use the feed as a read view of the authorized business calendar.
Organize an internal meeting as a business record
Create a timed or all-day event with a clear title, participants, location and notes. The organizer belongs to the group of active human workspace participants. Customer and project references can explain the purpose, while their own access checks remain in force. Updates use the current record version, and an event that no longer takes place is explicitly cancelled rather than silently removed from the shared context.
- Timed and all-day internal events
- Participants, place and notes
- Customer or project context
Keep the group and conversation understandable
The event’s personal visibility determines who can read it, including its internal conversation. Posting in that thread and changing the meeting have their own permission rules. Preparation questions, replies and supported attachments can remain with the event, so the group does not have to reconstruct the discussion from private messages. Cancellation preserves the record and conversation for the participants who need to understand what changed.
- Personal event audience
- Event-specific internal conversation
- Cancellation with retained context
Read the broader calendar without losing source meaning
Month, week and day views can combine supported entries from enabled sources, with filters for appointments, events and other business dates. The workspace’s calendar settings provide timezone and week-start context where configured. A personal ICS feed gives a compatible client a read-only subscription in its supported date window. A source label or external subscription is not a replacement for checking the original booking, project or commercial document before changing it.
- Month, week and day views
- Business-source selection
- Personal read-only ICS feed
A concrete workflow
Define the meeting context
Choose the purpose, time or date range and the optional relevant business references.
Choose and inform the group
Select active participants and review the event before creation.
Prepare in context
Discuss event-specific questions in the internal conversation and keep relevant material there.
Review the calendar and maintain the event
Use the appropriate view, inspect source records and explicitly update or cancel the event when plans change.
An illustrative working example
Illustrative workflow: organize a delivery review
A project lead creates a timed internal review and links the accessible project. The participating colleagues prepare questions in its conversation. In the week view, the lead also checks customer appointments and a milestone from the enabled sources. If the review is cancelled, the group can still read the explanation on the event. A colleague using an external calendar can subscribe to their authorized feed without taking over the editing workflow.
Questions about this topic
Is every internal meeting visible to the entire company?
No. Internal event visibility is personal to the organizer and participants under the event rule, rather than automatically public to every workspace member.
Can the calendar replace the source booking or project record?
No. It helps inspect dates and reach the underlying work. The source record remains the place to review the relevant business details and authorized actions.
Does an ICS subscription allow external calendar edits?
The described feed is read-only. Two-way synchronization or write-back from every calendar client is not established by that feature.
Are automatic meeting transcripts part of this internal event function?
The event record and conversation are available capabilities. Planned live transcription and automatic meeting-derived outputs are separate and should not be inferred from them.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Calendar
Workflow concept: Plan read-only calendar visibility while keeping event ownership explicit.
Outlook
Workflow concept: Compare business dates with the team’s established calendar habits.
Microsoft Teams
Workflow concept: Prepare internal meeting discussions with real participants and checked agendas.