ls command(s) not scoped to user permissions

[claybarrett]

When I use the command panoptes subject-set ls I see what appears to be every subject set in the system, not just those within my project. Is this intended?

The command panoptes workflow ls behaves similarly.

I suspect the command panoptes subject ls doing the same thing, but I'm not patient enough to wait for it to query them all, and aborted it.

I also can list the workflows in other projects. I'm not saying this information should be private, it just seems unusual to have this much access to other project information. It may not be that I could do anything more than LS, I'm not brave enough to try activate/deactivate/delete on someone else's stuff.

[adammcmaster]

That is how the API is intended to work, though admittedly it's not all that useful from the point of view of the CLI. All users (including anonymous users) can list all public resources. The zooniverse.org website uses the same API, so this is how it's required to work for users to browse projects, etc.