You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given one or more relations and a subject, the goal of the Lookup API is to determine the object(s) for which the user has the given relation(s). The query should resolve by starting at the subject node in the Graph of Relations and doing a reverse traversal until all of the object nodes of the graph have been reached from the initial subject node.
The text was updated successfully, but these errors were encountered:
Yep, same idea. The goal is to be able to lookup a subjects specific relations to one or more objects in one or more namespaces. This differs from the Expand API which returns all subjects and subject sets having a certain relation to an object.
The lookup API will be better suited for front-end UI component filtering and authorization filtering, just to two name two examples.
Given one or more relations and a subject, the goal of the Lookup API is to determine the object(s) for which the user has the given relation(s). The query should resolve by starting at the subject node in the Graph of Relations and doing a reverse traversal until all of the object nodes of the graph have been reached from the initial subject node.
The text was updated successfully, but these errors were encountered: