Persistent Room directory
Rooms remain inside the Community for specific topics and teams; authorized users can manage their names and order.
The Sesoba product
Sesoba offers persistent Community and Room context instead of temporary meeting links. Preview a Room, join it, work with voice and screen sharing, then continue through chat.
Community model
A Community is the shared scope for membership, roles, settings, and the Room directory. Users open an available Community and see its Rooms, members, and current state.
Rooms remain inside the Community for specific topics and teams; authorized users can manage their names and order.
Access is evaluated against active Community membership and the permissions needed for an operation.
Authorized users can review Community members and safe status information in a separate directory.
Preview, join, switch
Selecting a Room lets you preview its context and participants. Joining changes your active Room context. Browsing the workspace and entering a conversation remain deliberate, separate actions.
See participant count, sharing state, and Room context before entering.
Once joined, voice, microphone, deafen, and screen-sharing controls follow the active context.
Moving to another Room leaves the previous participation cleanly; voice and screen sharing do not move automatically.
End the active participation while continuing to see the Room directory and Community context.
Voice, screen, and chat
Voice provides fast coordination, screen sharing creates a common working surface, and persistent Room chat keeps notes and decisions available over time.
Speaking, microphone-muted, and deafened states are visible in participant cards.
One active share in the Room can be viewed in an expandable stage; the ability to start sharing can be restricted by role and Community policy.
Server-backed Community Rooms can load message history and keep conversation attached to Room context.
Roles and permissions
Sesoba uses Owner, Admin, Member, and Guest roles for Community administration. An Owner can delegate separate permissions for channels, invites, members, roles, settings, audit access, and Room moderation.
Carries primary responsibility for the Community and has a protected ownership boundary.
Acts only through delegated administration permissions; full control is not automatic.
Receives normal trusted use and communication capabilities allowed by Community policy.
Is evaluated with narrower access; chat and voice may depend on Community settings.
Participant moderation
Authorized users can moderator-mute a participant, release that mute, or remove the participant from the current Room. Community-level kick and ban are separate, broader administration actions.
Audio Settings
The main Room surface focuses on daily microphone, deafen, and screen-sharing controls. Audio Settings bring together microphone selection, live level, a local recording check, input gain, echo cancellation, noise suppression, and automatic gain control.
Speaker output currently follows the Windows and embedded web runtime system output.
Client status
The current product runs on Windows desktop and provides Turkish and English interfaces. Public download, mobile apps, and automatic updates are not currently promised.
Public access is not enabled; you can review the current pilot and deployment directions.