The Sesoba product

You do not just call a Room. You work inside it.

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.

  • Windows desktop
  • Turkish and English
  • Controlled pilot
  • Server-authoritative model
Sesoba
Selected RoomDesign Desk
PreviewJoin Room
In this Room4 participants
AD
Ada DemirSpeaking
MK
Mert KayaMicrophone muted
DA
Deniz ArasVoice connected
Screen sharing ready
Weekly product flow
Voice connected
Product interface presentation derived from the current Sesoba Windows client.

Community model

People, Rooms, and administration share one boundary.

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.

01.1

Persistent Room directory

Rooms remain inside the Community for specific topics and teams; authorized users can manage their names and order.

01.2

Membership context

Access is evaluated against active Community membership and the permissions needed for an operation.

01.3

Member directory

Authorized users can review Community members and safe status information in a separate directory.

Preview, join, switch

The selected Room is not necessarily the joined Room.

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.

Sesoba
Selected RoomDesign Desk
PreviewJoin Room
In this Room4 participants
AD
Ada DemirSpeaking
MK
Mert KayaMicrophone muted
DA
Deniz ArasVoice connected
Screen sharing ready
Weekly product flow
Voice connected
Product interface presentation derived from the current Sesoba Windows client.
02.1

Room preview

See participant count, sharing state, and Room context before entering.

02.2

Joining voice

Once joined, voice, microphone, deafen, and screen-sharing controls follow the active context.

02.3

Switching Rooms

Moving to another Room leaves the previous participation cleanly; voice and screen sharing do not move automatically.

02.4

Leaving a Room

End the active participation while continuing to see the Room directory and Community context.

Voice, screen, and chat

Three complementary layers in the same Room.

Voice provides fast coordination, screen sharing creates a common working surface, and persistent Room chat keeps notes and decisions available over time.

03.1

Drop-in voice

Speaking, microphone-muted, and deafened states are visible in participant cards.

03.2

Screen sharing

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.

03.3

Persistent Room chat

Server-backed Community Rooms can load message history and keep conversation attached to Room context.

Roles and permissions

Built-in roles with narrow Admin scope when needed.

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.

Owner

Carries primary responsibility for the Community and has a protected ownership boundary.

Admin

Acts only through delegated administration permissions; full control is not automatic.

Member

Receives normal trusted use and communication capabilities allowed by Community policy.

Guest

Is evaluated with narrower access; chat and voice may depend on Community settings.

Participant moderation

Room actions are tied to current participation.

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

Daily controls stay compact; testing tools live separately.

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

A working bilingual desktop client for Windows.

The current product runs on Windows desktop and provides Turkish and English interfaces. Public download, mobile apps, and automatic updates are not currently promised.

TR / EN

Evaluate the product through a controlled pilot.

Public access is not enabled; you can review the current pilot and deployment directions.

Pilot information