I think this could do with more explanation. What is 'member' in this context? And 'role'? There's nothing in the function name or docstring or the location of the function to suggest this has anything to do with groups or organizations.

Arguably these could have been more clearly named as two functions `organization_roles_list` and `group_roles_list` (both calling `_roles_list`). Anyone grepping the api docs for "group" or "org" to find everything you can do with groups or orgs will not find this. The fact that groups and organizations share some code is an implementation detail that should not have been allowed to show through in the interface or API imo.

But without renaming functions, we can at least clarify it in the docstring.