I can say with some degree of certainty, that some of you, perhaps a significant proportion, are likely Spying for Another Entity, possibly betraying your current Corporation or Alliance, and without you even realising it.
*
I call this situation, the INADVERTENT SPY.
Many moons ago, I found myself helping a number of Corporations with their Recruitment & Retention Processes & Strategies.
I discovered something particularly strange. And concerning. And with each Corporation I helped there was the same pattern that existed.
In one case I discovered a Corp CEO was spying on his own Corporation and he didn’t have clue. He was extremely embarrassed by this.
*
SO WHAT ON EARTH WAS GOING ON??
It’s quite simple. ESI Background checks, and not just that, but ONGOING ESI authorities were still reporting to a previous Corporation or Alliance. In some cases several previous entities.
*
WHY?
Because A new recruit, (or CEO starting a corporation in that case) OFTEN FORGETS to REVOKE an ESI Access Permission (also known as an API KEY) given to a previous Corp or Alliance.
*
YES – FORGETS.
And in the case of new recruits, CORP RECRUITERS often fail to check with the recruit to see what existing ESI Scopes that recruit has active.
*
IF YOU ARE A RECRUITER, DO YOU ROUTINELY CHECK FOR THIS ?
Many Do Not, and an INADVERTENT SPY inserts himself into your corporation.
I found examples of countless directors and recruiters who were totally unaware of this problem.
*
HAVE YOU FORGOTTEN TO REMOVE YOUR PREVIOUS ESI SCOPES?
If you are unsure, I suggest you go check, immediately after reading this post.
*
WHEN YOU JOINED YOUR CURRENT CORPORATION, WERE YOU ASKED TO CHECK?
In many cases, too many, that will be a No.
*
THE SOLUTION.
The solution to this common problem is to ensure that your Corporation’s Recruitment Policy includes an “Existing ESI/API Check” when onboarding.
To make this an easy process, I produced a document that proved really useful,
AND I AM SHARING that Document with you now.

Thanks to the Digital Media Guy for the great artwork.
https://jumpsector.space/evething/pdf/spydoc
With the above link you should be able to View / Download the PDF file.
Feel free to make any changes to customize to your own requirements or use as inspiration for your own onboarding document.
Should you require a professional touch, and have it personalized to a high standard, please contact the Digital Media Guy, his email address is at the end of the document and he is willing to help.
*
THE DOCUMENT – HOW TO USE
The document is designed to be issued to a new recruit at the onboarding stage, and gives instructions on how to clear the unwanted ESI authorizations.
It may prove useful to have either the recruiter and/or the recruit share their screens, to ensure the process is completed correctly.
By implementing this procedure as standard, the Inadvertent Spy should not arise.
It also makes sense to ensure that you purge ESI authorisations amongst your current membership regularly too, to deal with any instances that have fallen through the cracks.
*
Sincerely hopes this helps somebody.
Take Care, Fly Safe.