Sometimes something you have spent years building can just go to hell. Not because you are an idiot. Not because you did everything wrong. Just because that is how it turned out.
In my case, it was LinkedIn. At some point, the service decided that something suspicious was happening with my account, restricted access, and asked me to verify my identity. I was ready to do that, but the only verification method available did not accept documents issued by my country.
Then came the very modern quest: LinkedIn sends you to Persona, Persona sends you back to LinkedIn, and the account stays locked the entire time.
An important note
This is not a guide to bypassing verification, nor an attempt to argue that LinkedIn must restore my account. It is a breakdown of one recovery flow based on my correspondence with LinkedIn and Persona.
I will not publish my email address, document contents, links from the verification emails, or other data that could help someone access the account. I am keeping the case numbers because they distinguish this incident from a generic story.
What happened
On September 8, 2026, I contacted LinkedIn about my account. In the form, I reported unusual activity, confirmed that the account belonged to me, and said that I had lost access.
LinkedIn replied that, because I had reported possible compromise, the account had been temporarily restricted while they investigated. To recover access, I was asked to complete identity verification through Persona and upload an identity document.
The problem appeared immediately: the proposed process did not accept Russian documents.
I did not refuse verification. I offered to prove account ownership another way: through the email address and phone number attached to the account, previous profile information, account history, or a manual review by a support representative.
I am not publishing the case number.
What LinkedIn said
On September 11, Trust Ops replied that its verification system did not accept documents issued by certain countries. Since my document fell into that category, LinkedIn could not continue the appeal and the account would remain restricted.
I asked whether there was an alternative path:
- manual review by a Trust & Safety specialist;
- verification through the email address associated with the account;
- verification using previous account information and activity;
- a secure way to submit documents directly to LinkedIn;
- escalation to Account Recovery or Trust Operations.
The answer was repeated: the current process did not accept documents from certain countries, the appeal could not continue, and access could not be restored.
This distinction matters. I was not told, “We checked your documents and found a mismatch.” I was told, “Documents in this category are not supported by the current process.”
The problem was not that the owner refused to prove their identity. The proposed verification channel simply could not accept the available document.
Why I contacted Persona
I wanted to clarify where the limitation lived: in Persona’s general supported-document list, or in LinkedIn’s specific configuration.
I asked Persona whether the following documents were supported for this scenario:
- a Russian international passport;
- a Russian domestic passport;
- a Russian driver’s license.
I am not publishing the Persona case number.
At first, I received general FAQ links. After a follow-up, a Persona support agent gave a more specific answer: Persona does not manage LinkedIn account access, restrictions, or recovery. It cannot manually verify my identity, reset the process, issue a new link, or escalate a LinkedIn recovery request.
Persona also explicitly asked me not to send them a copy of my identity document: they cannot process such documents manually outside LinkedIn’s verification flow.
The result was a closed loop:
Why the usual advice did not help
In situations like this, people usually recommend:
- changing the password;
- enabling two-factor authentication;
- checking the email account;
- opening a support case;
- completing verification through the provided link.
Some of these steps are useful. If compromise is suspected, the email password should indeed be changed. But none of them solves the problem when the account is already restricted and the mandatory identity-verification channel does not accept the owner’s document.
In my case, the bottleneck was not that I did not know which button to press. The bottleneck was the absence of an available way to prove account ownership.
What you can try
This is not a promise of a result. It is a careful sequence that helped me build a clear evidence trail.
1. Save the entire correspondence
Keep:
- the original email with the case number;
- the response explaining the restriction;
- all follow-up messages;
- replies from the verification provider;
- dates, case numbers, and case statuses.
Do not rely on memory when quoting support. In my case, the key wording was LinkedIn’s statement that documents from certain countries were not supported.
2. Separate responsibilities
Write down which company can actually take the next step.
Persona may operate part of the verification flow, but it does not control access to a LinkedIn account. The recovery request therefore has to remain with LinkedIn, even if the technical verification window is provided by Persona.
3. Ask for a specific procedure
Instead of simply saying “please restore my account,” ask for:
- manual account ownership verification;
- review by Account Recovery or Trust Operations;
- an alternative secure document-submission channel;
- verification through email, phone, and previous account information;
- written confirmation that no alternative process exists.
The last request is uncomfortable but useful: it turns an endless exchange of links into a clear answer about the limits of the process.
4. Do not open multiple identical cases without a reason
Persona explicitly recommended continuing in the existing LinkedIn case and warned that additional requests could cause further delays.
If a new case is necessary, include the old case number and a short timeline instead of starting the story from scratch.
5. Request the account data separately
If recovery is genuinely impossible, you can separately ask how to obtain the personal data associated with the account: profile information, connections, messages, and account history. This is a different request. It is not “restore my access,” but “explain how I can obtain my data and what privacy procedures are available.”
This does not guarantee account recovery and is not legal advice. But account access and access to personal data are different questions, and it helps not to mix them.
What not to do
Do not:
- use someone else’s passport or account;
- claim a fictional country of residence;
- send documents to random intermediaries;
- try to bypass verification with forged documents;
- publish verification links in an open channel;
- send an identity document to Persona when Persona has said it cannot process it manually.
An attempt to bypass the restriction can turn a difficult recovery case into a clear rules violation and create additional personal-data risks.
What makes this especially infuriating
The worst part is not just losing access to a website. It is realizing that years of work, contacts, conversations, and professional history can disappear from your life not because you made a mistake, but because of a limitation in somebody else’s automated process.
You can be the legitimate account owner. You can reply from the same email address, know the profile history, and be ready to show your documents. But if the required button does not work for your country, the system behaves as if that is not enough.
And yes, it is infuriating. Not because I want special treatment. Because I want at least one working path for a normal person trying to prove that they are who they say they are.
What I learned as an engineer
There is an unpleasant product lesson in this story.
A system can be correct from the perspective of each individual component and still fail to provide a working end-to-end flow.
LinkedIn checks account ownership. Persona provides verification infrastructure. But if the document set is unsupported and there is no alternative route, the user ends up between two systems. Each side can honestly say, “This is outside our scope,” while recovery remains impossible.
The user does not care about one component or the existence of a form. The user needs a complete path:
In my case, that path broke at the third step.
Current status
As of publication:
- The LinkedIn case was closed with a response that documents from certain countries are not supported and the account would remain restricted;
- The Persona case was closed with an explanation that Persona cannot manually verify identity or escalate LinkedIn recovery;
- no alternative recovery flow was offered.
The next possible step is to ask someone with an active LinkedIn account to open a new support case, reference the old number, and request a manual escalation. This is not guaranteed to work, so in parallel it makes sense to keep professional contacts distributed across GitHub, a personal website, job platforms, Telegram, and other channels.
The practical conclusion is simple: do not make one platform the only archive of your professional life. Keep your resume, project list, contacts, work links, and record of achievements separately.
Because sometimes something you spent years building really can just go to hell. Not because you are an idiot. Just because that is how somebody else’s service is built.
LinkedIn can be an important channel. But a channel is not a backup.