Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Future Consideration
Workspace Notes
Created by Guest
Created on Oct 3, 2025

Improve Handling of Restricted Meetings in Notes Client and HCL Verse VOP

As a User, I need to be able to create a meeting using DOMI that uses the invitees of the calendar invite as the only allowable meeting members, because only the people invited should be allowed to attend a restricted meeting.


When a user creates a calendar meeting from the Notes client or HCL Verse VOP with a limited set of participants (a restricted meeting), the field is neither properly populated nor flagged.

The purpose of a restricted meeting is to ensure that only specific invited participants can attend (for example, a private meeting with one’s manager). However, if another colleague discovers the meeting URL, they are still able to join, which defeats the purpose of the restriction.

We request that the integration between HCL Notes and HCL Verse be enhanced to ensure restricted meetings are correctly enforced, so that only the intended participants can access and join such meetings.

  • Attach files
  • Admin
    Timothy Clark
    Jan 2, 2026

    It has to be said that, if this is DOMI & Sametime (not mentioned at all in the idea), then the manager running the 1:1 does have the option of locking the meeting when the other person has joined the call.

    Standard function of a Sametime meeting, just needs to be used by the manager.

    Also it's not clear if the meeting is created using DOMI as a unique meeting or using an existing meeting that everyone would already know about. E.g. https://sametime.com/meetings/tims_meeting. DOMI created meeting has a very unique meeting address, which would be very hard/impossible to guess unless one of the peoples calendar has been accessed nefariously. At that point there is probably nothing we can do to improve the situation apart from advise on better password security.

  • Guest
    Oct 6, 2025

    must be a top level priority this integration