> ## Documentation Index > Fetch the complete documentation index at: https://docs.polymorfa.com/llms.txt > Use this file to discover all available pages before exploring further. # Inspector ownership and devices > Open an exact WhatsApp session as a persistent native linked device. The Polymorfa account that completes native pairing owns one exact real or testing session through Inspector. Ownership does not add team, project, or session-control permissions. Those permissions continue to come from the account's live team membership and project role. ## Open a testing session 1. Install and authorize [Polymorfa Inspector](/desktop-app/install). 2. Sign in and select the team that owns the Sandbox project. 3. Find the project and testing number on the Inspector home screen. 4. Choose **Open**. Inspector opens the session as a native linked device. If the session is already open on this device, **Open** returns you to the existing session. Before the first production session opens, Inspector warns that it can act as and send from the real WhatsApp number. Closing the Inspector window, restarting the app, retrying a failed connection, or signing out of the dashboard keeps the native linked device. Reopening the number on the same computer reconnects with its retained native identity without another pairing step. Inspector and the Console show **Owned by *name*** and that member's account photo when available. Raw device identifiers are not displayed. Other authorized project members can see the owner but cannot silently replace it. ## Filter by Customer Inspector shows the Customer assignment on each session row, next to the phone and session ID. Use the **Customer** filter to show only sessions assigned to one exact Customer. Customer and **Owned by** remain separate: Customer names the person or business that the Number belongs to, while **Owned by** names the Inspector user who controls the native linked device. Inspector accepts a Customer assignment only when it belongs to the selected project and session. If that tuple changes while a session opens, Inspector stops instead of attaching the wrong Customer metadata. A valid assignment is kept when the app reconnects or restores a retained session. ## Remove or transfer a session Removing a testing number closes its active Inspector connections, invalidates its retained devices, and clears its simulated state. An authorized ownership transfer invalidates the previous owner's Inspector devices before the new owner can pair. Ordinary app close, retry, and dashboard sign-out do not unlink the device. ## Troubleshooting * Choose **Refresh** when a newly created testing number does not appear. * Confirm that the selected team still owns the project. * Confirm the expected account appears under **Owned by**. * If **Open** fails, retry once, then follow [Inspector troubleshooting](/desktop-app/troubleshooting). List and manage testing numbers. Download and authorize the desktop testing app.