Community-scoped access
The server evaluates membership and relevant Community context for authorized operations; it does not trust client-reported state alone.
Security and deployment
Designed for controlled access; validation continues.
Sesoba makes only the security claims supported by the current product direction. The product remains in a controlled pilot stage, and production hardening is ongoing.
Current security status
- Security testing and production validation remain in progress.
- No end-to-end encryption claim is currently made.
- No security certification claim is currently made.
- Public availability remains controlled.
- Broader production hardening continues.
Roles and delegated permissions
Owner, Admin, Member, and Guest roles are available. Admin permissions can be scoped separately for channels, invites, members, roles, settings, audit access, and Room moderation.
Participant moderation
Authorized users can apply moderation actions tied to current Room participation; broader membership actions require separate Community permissions.
Audit-oriented events
A persistent event design supports reviewing successful administration and moderation decisions within a Community. This is not a claim of a certified audit product.
Persistent storage and backup direction
Server-backed Community data and Room chat follow a persistent storage direction; backup responsibilities must be made explicit for dedicated deployments.
Hosted and Private deployment
Hosted represents a managed infrastructure direction, while Private represents a deployment dedicated to an organization. Final security and operating scope for either model is defined during pilot evaluation.
Security reporting
The official support channel accepts responsible reports.
Technical or security reports may be sent to support@sesoba.com. Do not share passwords, tokens, invitation codes, or production access secrets.