Workspace-scoped access
The application API checks workspace membership when accessing product objects. A remembered workspace or application selection in the desktop is a convenience, not authorization.
Security & data
Clear boundaries.
Informed decisions.
A practical overview of the controls implemented in the product and website. For deployment-specific requirements, confirm the configuration with your SignalShip administrator.
Desktop credential handling
The desktop keeps its API credential in the main process and uses the operating system’s secure storage where available. It informs users when secure storage is unavailable.
Evidence with context
Product views retain the application, flow, and observation context supplied by the service. Missing captures or incomplete run evidence are shown as unavailable, rather than represented as a successful result.
A deliberate website boundary
Website account access uses the existing SignalShip identity service when enabled. Website sessions use an opaque HttpOnly cookie; the application API credential is not returned to browser scripts.
Use test accounts and appropriate application data for exploration. Hosting, data retention, approved releases, and external service access depend on your deployment. This page does not assert a compliance certification or enterprise SSO support.