Fields
Core Fields
Plan Features
Billing Configuration
System Fields
Relationships
Validation Rules
- Name must be unique per organization
- Price must be >= 0
- Grace period: 0-30 days
- At least one active plan must exist
Features
Membership Plan
Acceptance Criteria
Frontend
- Admin/client UI can view and manage
Membership Planrecords where applicable.
Backend / API
- CRUD operations exist for
Membership Plan(create, read, update, delete/archive).
Permissions
- Access is restricted to appropriate roles (tenant-scoped).
Business Rules
- Fields and relationships documented on this page are enforced for
Membership Plan.
Error Handling
- Invalid payloads return field-level validation errors.