When you install a managed package with a post-install script, Salesforce creates a special ghost user under which all of the post install activities occur. I think this is undocumented. Here are some details.
This can be great from an audit point of view (you can see which package has 'touched' all the data). But can problematic in several examples:
- Certain objects are inaccessible by SOQL (I've found
CronTriggerandApexClassso far) - Scheduled Jobs (and any code they call) will forever run under the post-install context,
- Batch Jobs execute as the post-install user and suffer the same issues above,
I've tried querying the user by id in SOQL to no avail, and the debug log monitor don't record anything.
How crippled is this special ghost user? Does he have a documented profile?
Edit: I've emailed myself some post install context UserInfo return values. Interesting ones in bold:
- UserType:
LicenseManager(Aha! Who knows what privileges he has!?) - ProfileId:
00eF0000000XXXXAAA(viewing URL gives Insufficient Privileges!) - UserName:
033g0000000XXXXAAA@00df0000000XXXXAAA(package-id@org-id) - UserId:
005F0000003XXXXAAA(viewing URL gives Insufficient Privileges!) - Email:
[email protected] - DefaultCurrency:
USD - FirstName:
null - Language:
en_US - LastName:
[managed package name] - Locale:
en_US - Name:
[managed package name] - OrganizationId:
[installing org id] - OrganizationName:
[installing company name] - SessionId:
null - TimeZone:
America/Los_Angeles - UiTheme:
Theme3 - UiThemeDisplayed:
Theme3 - UserRoleId:
null
