> OptionalSubjectRelation won't return member or admin; it allows you to refer not to the subject itself, but to a use of a subject's relation as the overall subject. What I said is without specifying

OptionalSubjectRelation

in

LookupSubjects

and not returning

member

or

admin

which is an object type. > To answer your original question: no; we don't return how a subject is found in LookupSubjects. For that, you'll want to take a look at the Expand API, but it has to be invoked recursively yourself But what is the purpose of

OptionalSubjectRelation

which is optional? Returning just a bunch of

subject_object_id

when

OptionalSubjectRelation

is not set could not help developers, in this case, developer needs to store this relationship somewhere else to find out which

subject_object_id

is belongs to which relation/role. - With

OptionalSubjectRelation

set, developer knows the returned `subject_object_id`s belongs to which relation/role. - With

OptionalSubjectRelation

not set, there is no way to know returned `subject_object_id`s belongs to which relation/role (By other way, it is a design problem and less usable). What is the technical problem here that you cannot put

subject_object_type

(relation) in

LookupSubjects

response?