The current rules for importing assets by Content are as such.
To prevent misuse, AssetService:CreateEditableImageAsync() only allows you to load and edit image assets:
That are owned by the creator of the experience (if the experience is owned by an individual).
That are owned by a group (if the experience is owned by the group).
That are owned by the logged in Studio user (if the place file has not yet been saved or published to Roblox).
Using the thumbnail content URI : ‘rbxthumb://’, no such restrictions exist although the thumbnail is literally the same as the actual asset. except I believe you’d have to specify the resolution which may mismatch.
Expected behavior
For example this would not be allowed
local AssetID = 6553589977
local Editable : EditableImage = AssetService:CreateEditableImageAsync(`http://www.roblox.com/asset/?id={AssetID}`)
But this would, because thumbnails aren’t owned by any users and are just generated by ROBLOX for use in marketplace.
local AssetID = 6553589977
local Editable : EditableImage = AssetService:CreateEditableImageAsync(`rbxthumb://type=Asset&id={AssetID}&w=420&h=420`)
Considering they are the same asset, there is clearly an issue here.
A private message is associated with this bug report