To get a list of all nested objects inside a namespace called

org

, you can use Ory Keto's list API. The list API allows you to query relationships based on partial relationships. You can refer to the [gRPC](https://www.ory.sh/docs/keto/reference/proto-api) and [REST](https://www.ory.sh/docs/keto/reference/rest-api) API reference documentation for all details. Here's an example of how to use the list API with a partial relationship query: 1. Set the

namespace

field to "org". 2. Leave the

object

,

relation

, and

subject

fields empty or optional. This will return a list of all relationships within the "org" namespace. For more information on how to use the list API and partial relationship queries, you can refer to the [List API: display all objects a user has access to](https://www.ory.sh/docs/keto/guides/list-api-display-objects) guide and the [ListRelationTuplesRequest.Query](https://www.ory.sh/docs/keto/reference/proto-api#listrelationtuplesrequest-query) documentation.

To find all permissions a subject has across namespaces, you can use Ory Keto's list API. You can query relationships based on partial relationships to get the permissions for a specific subject. You can refer to the [gRPC](https://www.ory.sh/docs/keto/reference/proto-api) and [REST](https://www.ory.sh/docs/keto/reference/rest-api) API reference documentation for all details. Here's an example of how to use the list API with a partial relationship query: 1. Leave the

namespace

,

object

, and

relation

fields empty or optional. 2. Set the

subject

field to the subject you want to query permissions for. This will return a list of all relationships involving the specified subject across all namespaces. For more information on how to use the list API and partial relationship queries, you can refer to the [List API: display all objects a user has access to](https://www.ory.sh/docs/keto/guides/list-api-display-objects) guide and the [ListRelationTuplesRequest.Query](https://www.ory.sh/docs/keto/reference/proto-api#listrelationtuplesrequest-query) documentation.