Show all clients you have scope to manage

[jonasfj]

We have some heuristic to create a default filter on clients in the client inspector...

I suggest we make a checkbox "show clients you can manage" (or some better wording).

But it being so that it uses the scopes you have to determine which clientIds you can modify, and only shows you those clients... This requires the inspector to understand scopes used by taskcluster-auth.

Note, there is a proposal to simplify these scopes in: taskcluster/taskcluster-rfcs#99

[djmitche]

I don't object, in principle, to tools modeling the scope requirements for API calls. I like the idea of a button, too.

Currenty we don't ever look at the user's scopes and adjust the UI on that basis [*] -- we just blindly make the API call and show the resulting error. I think our users would appreciate changing that behavior, but if we do so we should do it consistently through all of the tools, so users are not forced to remember where scopes are accounted for and where they are not.

I think @eliperelman is considering changing this in the refactor?

[*] actually, I think private artfacts are an exception..

[eliperelman]

This probably won't happen immediately in the photon work, but long-term, yes, we want more UI guarded by scopes.