A service account represents a workload rather than the employee who happens to deploy it. Give the identity a clear purpose and keep its permissions separate from human administration. A useful name helps a reviewer, but it doesn't grant access on its own.
The fictional receipt and catalog tasks create local identity records and inspect the selected project. These records aren't credentials and the browser never authenticates a real caller. Production access still needs the correct binding, scope and applicable service controls. Where a workload can use an approved identity-based workflow, evaluate that instead of distributing a permanent key to every machine or person.
Create a workload identity before reviewing its resource permissions.