OpenSlides is a digital motion and assembly system. A deployment can hold participant accounts, meeting groups, motions, elections, files, chat messages, and presentation material. The public dashboard may be intended for attendees or visitors, but the administrative and participant data sits behind a set of group permissions.
ZoomEye count-only measurements on 2026-11-09 between 23:46 and 23:47 UTC returned 776 assets for title="OpenSlides", 954 for the product name in the HTTP body, and zero for app="OpenSlides". The query used sub_type=all, page 1, and page size 1. These are matched records, not counts of active assemblies or exposed accounts.
The title and body counts are close. That is useful for discovery but does not establish a complete population. The missing application fingerprint means the index relies on page content. A title match may be a public meeting page, a login screen, or a documentation site.
Groups define what a participant can do
OpenSlides help documentation describes groups as the way to decide what a participant may do in a meeting. Administrators can assign participants to groups, and the permissions cover actions such as seeing names, reading files, using chat, managing motions, and accessing settings. The system also supports meeting-specific and organization-level roles.
The review should connect each account to its meeting and group membership. A participant who is no longer in the assembly should not retain access to files, motions, or internal notes. A group that was created for one committee should not inherit broad administration by default.
Files and chat deserve separate checks. The help center describes file and folder permissions and chat read/write rules by group. A public meeting page may be appropriate while an attached document is restricted. The permission decision should follow the object, not only the top-level event page.
Measurement method
The SDK requested one record per dork with sub_type="all", page 1, and page size 1. The measurement recorded exact totals and did not download complete asset records. The public search link uses the title query, which is the most informative public signal in this sample.
An authorized reviewer should confirm the application through the meeting page and the login path. The count cannot show whether a host uses SSO, whether local registration is enabled, or whether a public dashboard exposes participant names.
A review sequence for assembly operators
Inventory meetings and administrators first. Confirm that every active meeting has a responsible owner and that old meetings are archived or restricted. Review organization-level users separately from meeting participants.
Map groups to business roles. Test a view-only participant, a committee member, and a meeting administrator against the same motion, file, and chat object. The results should match the documented group model. Remove groups that no longer correspond to a committee or staff role.
Review participant imports and exports. A CSV import can create accounts and assign groups. An export can reveal names, email addresses, membership, and attendance. Restrict these operations to the people who need them and retain an audit trail.
Check public and internal projections. A public dashboard may be intentional, but an internal projector or a file link should not bypass the meeting boundary. Confirm that URLs do not share access through an unauthenticated static path.
What the title count can support
The 776 title matches and 954 body matches show that OpenSlides is discoverable by page content. They do not prove that every meeting is public, that every account is active, or that a permission setting is wrong. The zero app count is an index limitation.
The useful next step is to connect product discovery to group membership. OpenSlides makes that mapping explicit, which is an advantage. A defender can test the actual participant experience and record whether the group, meeting, file, and chat boundaries hold.