Hi Vlad S., did you notice any difference? As I understand UI around service account, you can assign project when SA is being created on org level, but also manually assign it to the project on project level settings.
However, I have a lot of issues with service account created on org level with Member privileges (not org Admin). This SA behaves odd. Sometimes it works, next several api calls return errors, then next one works.
And response from import API is odd too, {"error":"not a project member","status":0}
Status 0 is not allowed response code from import API.
But, when I use another service account created on org level as org admin, where assignment to project inherits from Organization role, this service account works perfect for every API call.
