PEOPLE & MEETING ACCESS
Make participation an explicit part of the meeting.
Choose active team members for an internal event and keep participation separate from the right to change the meeting or post in its conversation.
Project review
Visible to the permitted event audience
Being part of a meeting is not the same as managing it
A colleague may need to attend and read the context without having authority to move or cancel the event. Internal scheduling works best when those differences are clear. Tsumira records participants as team memberships and checks their availability as active human members. The organizer also belongs to the participant set, giving the event a defined group of people rather than an unbounded public audience.
Select actual active people from the workspace
Participant identifiers are checked against active human memberships in the same workspace. The system does not simply discard invalid entries and pretend the intended group was fully invited. The organizer is always included, and the supported participant limit applies to the total. Review the selected people by identity before creating or changing the event, especially when colleagues have similar display names.
- Active human team members
- Organizer included in participation
- Validation of the intended group
Keep meeting visibility personal
The schedule event uses a personal visibility rule in addition to the ordinary workspace access boundary. The calendar and daily contributions show the current viewer’s meetings under that rule. Being a workspace member does not mean every internal event becomes a public company notice. When the group changes, review whether the remaining participants are the intended audience and whether related customer or project information is actually accessible to them.
- Viewer-specific event visibility
- Personal calendar contributions
- Separate related-record access
Distinguish attending, editing and writing
Reading an event as a participant does not itself grant the right to move it. Updates and cancellation follow the organizer or authorized management rule. Writing in the event’s internal conversation has its own permission, separate from changing the meeting details. These distinctions support a practical setup where somebody can read background without changing the schedule, or join the discussion without taking over responsibility for organizing the event.
- Read access separate from editing
- Organizer and management change rule
- Separate conversation-posting permission
Project review
Attendance and the permission to change or discuss an event are checked separately.
A concrete workflow
Identify the intended meeting group
Choose the colleagues who genuinely need to participate, including the organizer.
Validate the selected people
Use active workspace members and review their identities before accepting the group.
Check the context and access
Consider the event audience and any separately protected customer or project references.
Maintain participation deliberately
Review changes to the group and preserve the distinction between participant, organizer and conversation rights.
An illustrative working example
Illustrative workflow: include a colleague for context
A delivery lead organizes an internal review and includes a colleague who needs to read the discussion but is not responsible for the schedule. The event keeps that person in its participant group while the relevant editing and conversation permissions remain separate. If a customer record is linked, the team does not assume that attendance alone opens the full customer history.
Questions about this topic
Can the organizer be absent from the participant set?
The implemented event rules include the organizer as a participant. They are part of the defined audience of their meeting.
Can an inactive membership be silently accepted?
Participant validation checks active human memberships in the workspace and refuses an invalid intended group rather than quietly dropping entries.
Does attendance grant permission to reschedule?
No. Reading as a participant and changing the event are separate. The applicable organizer or authorized management rule controls updates and cancellation.
Does event access automatically reveal a linked customer?
No. Linked customer and project context still follows its own access checks. Meeting participation is not a blanket related-record grant.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Microsoft Teams
Workflow concept: Confirm the human participants who actually need the internal event.
Slack
Workflow concept: Clarify attendance responsibility before adding colleagues to a meeting.
Google Calendar
Workflow concept: Compare an attendee list without treating invitation as general workspace access.