Hi! I’m using Directus 12.6.0 with PostgreSQL for a multi-business app.
Business owners/staff are the authenticated users. They create jobs for their business’s customers. Customers are CRM records—they aren’t creating jobs themselves.
Customers belong to a business, jobs belong to a customer, and memberships link business users to businesses. Read policies already restrict these users to customers in businesses where they have an active membership.
How do I restrict job creation to those same customers using access policies alone?
When a business user creates a job with “{“customer”: “”}”, does Directus check that customer’s Read permissions, or must this be enforced separately in Create validation?
A nested “customer.business.memberships” validation rule rejects even authorised requests with “customer: Value is required”, despite supplying the ID.
What is the correct schema/permission configuration to handle this natively, without Flows or hook extensions? Or what is the supported native approach to ensuring a submitted customer ID belongs to a business the current user can access?