The prefix in your ObjectId, such as

Article:abcdefg12345

, is significant in Ory Keto and Ory Permissions, but not in the way you might expect. In Ory Keto, the namespace and the object are separate fields. The namespace is not inferred from the prefix of the object string. - Namespace: This is a separate parameter or field in your relationship tuple or API query. For example, you might have a namespace called

Article

. - Object: This is the identifier of the specific resource, such as

abcdefg12345

. When you define or query relationships, you should specify the namespace and object separately. The

Article:

prefix in the object string itself does not automatically set the namespace; it's just part of the object identifier if you choose to include it. However, the recommended practice is to keep the namespace and object separate and not encode the namespace into the object string. Example: - Namespace:

Article

- Object:

abcdefg12345

So, when querying with

ory keto

or

ory is allowed

, you should provide the namespace and object as separate arguments, not as a single string with a colon. The colon in the object string does not have special meaning for namespace resolution in Ory Keto. Instead, use the namespace field to specify the type (e.g.,

Article

) and the object field for the unique identifier (e.g.,

abcdefg12345

) [Objects](https://www.ory.sh/docs/keto/concepts/objects), [Namespaces](https://www.ory.sh/docs/keto/concepts/namespaces). Summary: The

Article:

prefix in your object string does not determine the namespace. Always specify the namespace and object separately in your queries and relationship definitions.