# Proxy and Session
Every connected LinkedIn account runs through its own IP address and its own saved session. Both live on the account row in **Settings**, on the **LinkedIn accounts** tab.
## The dedicated IP
When you connect a LinkedIn account, SDRPilot sets up a dedicated residential IP address for it before signing in. That address is used only by your account and stays the same, the way your home or office connection would.
This is not optional. LinkedIn treats a well known datacenter address as a red flag, and a sign-in from one is the fastest way to lose a session. SDRPilot refuses to sign in for an account that has no usable IP address yet.
## Country matching
During the connect flow you answer **Where do you normally use LinkedIn?** SDRPilot guesses from your browser, so check it before continuing. The address is bought in that country, and in a city inside it where one is available.
If no address is available in the country you asked for, SDRPilot uses the nearest sensible country instead, normally in the same region and within a few hours of your timezone. The account row then shows where the address actually is, so you always know.
The row reads something like **Runs on a dedicated IP in Amsterdam, the Netherlands**. While the address is still being set up it reads **Dedicated IP being set up**.
## Bringing your own proxy
You can use your own proxy instead. Choose **Use my own proxy** on the account row and enter its details. Your own residential or ISP proxy then replaces the dedicated address this account connects through. Datacenter proxies are rejected.
You can switch back to a SDRPilot address later. Both changes ask you to confirm first.
An account has to be signed out before its IP address can be changed. A live LinkedIn session cannot move to a new address without looking like a stolen session, so the control is locked while the account is connected and tells you so.
## Session health
The session is the sign-in SDRPilot holds for you. It is encrypted at rest and it carries one fixed identity, meaning one browser fingerprint, one timezone and one language, captured at sign-in and reused for everything after it.
On the account row you can:
* **check sign-in**, to confirm the session is still alive right now
* **sign in again**, when LinkedIn has ended it
* **sign out**, to stop all activity on that account without deleting anything
* **remove**, to delete the account from your workspace
SDRPilot also checks each healthy account on its own, so a session that dies quietly is noticed rather than discovered days later.
When LinkedIn ends a session, SDRPilot emails the workspace owner once to say which account stopped and that its outreach and replies are paused. The account row shows the same thing, so you can act from whichever you see first.
## Reconnecting
If you ticked **Remember my password** when connecting, an account whose session is ended tries to sign itself back in once, after a short random delay. It is deliberately cautious:
* it never retries within half an hour of a sign-in that just succeeded
* it stops after two failures in a rolling day, and after four attempts in a rolling day whether they worked or not
* it does not try at all when the last sign-in needed a phone approval or an emailed code and no authenticator secret is saved, because nobody would be there to answer
While automatic reconnecting is in progress the account shows as restricted rather than disconnected. If it cannot finish, sign in again by hand from the same row. You can withdraw the saved password at any time with **Forget saved password**, and the saved authenticator secret with **Forget authenticator key**.