v0.51.0

One platform schema can serve every customer organization

Platforms no longer need to copy the same schema into every customer organization. When a platform key creates a session for another organization, Ablo now reads the schema from the platform’s project while keeping every row inside the customer’s organization.

const { token } = await ablo.sessions.create({
  user: { id: userId },
  organizationId: customerOrganizationId,
  can: { records: ['read', 'update'] },
});

Most platforms need no schema option at all. Migrations and advanced routing can still select one explicitly with schemaProject.

The sessions guide now draws a firm line between policy-scoped customers and separate customer organizations. Sync groups decide which changes travel; they do not authorize reads.