Build user for Visual Studio Online

Using visual studio online, do I need a separate user for the purpose of ferrying code/builds across machines. I understand that the built in service account builds code and can publish, but with things like Jenkins that require access tokens to retrieve source code (for projects like unity (no we are not able to use unity build)) I find it would be best to have a 'service' account where I can create personal access tokens that isn't tied to any one developer.

Do I need a 'build' user or is there another way to ferry code to Jenkins servers or using personal access tokens for deployment groups?

In my opinion, there should always one key per user:

• Security: If an employee will leave the company then the key could be revoked and the person who left the company cannot trigger builds anymore

• Access-control and responsibilties: developers from team b are allowed to deploy apps to the production environment of team b, while members of team a are responsible for their own app and are restricted to environment a.

StackExchange DevOps Q#1389, answer score: 1