SelfCapabilities manages the capability state for the self participant.
Capabilities are received from the server via call.joined events and determine
what actions the current participant is allowed to perform.
Each capability is exposed as both:
end$) for reactive state managementend) for immediate accessMember-level capabilities are accessed via the grouped self / member accessors:
capabilities.self.muteAudio (sync)capabilities.self$ (observable)When a new call.joined event is received, the capabilities state is
completely replaced (not merged).
Each capability is exposed in both forms on every page below — an
observable (e.g. end$) for reactive UI binding, and a synchronous
getter (e.g. end) for one-shot reads. The accessor cards below list
the observable; click through for both signatures plus an example.
DestroyableSelfCapabilities
Destroyable.constructor
Observable that emits when the instance is destroyed
Observable for device capability
Observable for end call capability
Observable for lock capability
Observable for other member capabilities
Observable for screenshare capability
Observable for self member capabilities
Observable for send digit capability
Observable for set layout capability
Observable for the full capabilities state
Observable for vmuted hide capability