The row goes and the team goes with it. The DELIVERIES stay, because they are the history of what a practice system took and disconnecting does not undo that, and so do the matters and the clients the sync wrote. The attributes the connector made are unbound and made inactive with their sets untouched, and the ones no entry ever carried are deleted with their sets and taken off every matter that named them; a standard's row the firm made is unbound and left as it was; a reconnect of the same system rebinds the ones that stayed. Connecting another system starts at step 1 again. Where the system keeps a session for the stored credential, it is ended there first, best effort: a system that cannot be reached does not stop the disconnect. For a system each member signs in to, every member's sealed session and their set of visible matters go with the row and NOTHING is sent to the practice system: the sessions there are the members' own. A firm connected to a system this service carries no adapter for answers the not-available 422.

Operator mount: an operator acting for the firm named in the path, as its oldest active admin, else its oldest active billing member; X-Six-Minute-Acting-As names them. 404 for no such firm, 409 urn:six-minute:problem:no-acting-member for one with neither.