What problem does it solve?
Crystallize permissions and access control can be difficult to design correctly, especially when you need to restrict sensitive fields while keeping integrations working.
Core Features & Use Cases
- UI vs API permissions clarity: Explain that UI read-only/hidden settings do not block API writes, so you must configure CRUD permissions for real enforcement.
- Role-based access design: Create and manage built-in and custom roles with the one-role-per-user constraint in mind.
- Field-level and resource-level control: Apply shape field permissions (read-only or hidden) and combine them with CRUD permissions for shapes, items, price variants, catalogue folders, topics, orders, and users.
- Access token strategy: Choose user tokens for role-scoped access or tenant-level API tokens for service-to-service integrations.
Quick Start
Use the permissions skill to design a role and token plan that enforces CRUD restrictions on sensitive fields while using UI locks only for editor experience.