​

Registrations Data Model

​

Overview

​

Complete Schema Reference

​

Visual Data Model

​

Core Entity Relationships

​

Key Relationships Explained

• REGISTRATION defines an event or program accepting signups
• CATEGORY organizes signup options (e.g., T-shirt size, Meal preference)
• SELECTION_TYPE provides specific choices within categories

1. Person creates a SIGNUP for a registration
2. ATTENDEE(s) are added (self or others)
3. SIGNUP_TIME(s) specify when attendees will participate
4. SIGNUP_LOCATION(s) define where events occur
5. EMERGENCY_CONTACT(s) provide safety information

• PERSON is the signup submitter (from People module)
• ATTENDEE can be the submitter or someone else (child, guest, etc.)
• One signup can include multiple attendees
• Each attendee has their own emergency contacts

• SIGNUP_TIME tracks session/workshop times
• SIGNUP_LOCATION tracks event venues
• Both linked to parent signup, not individual attendees
• Supports multi-day, multi-location events

• Campus associations via registrations_registration_relationships
• Additional metadata via relationship tables

​

Query Requirements

​

Schema Prefix

​

Row Level Security (RLS)

• tenant_organization_id: You only see data for your current organization
• system_status: You only see ‘active’ records by default

• ❌ WHERE tenant_organization_id = 1 (unnecessary)
• ❌ WHERE system_status = 'active' (unnecessary)

​

Entity Tables

​

registrations_signups

​

registrations_attendees

​

registrations_registrations

​

registrations_categories

​

registrations_selection_types

​

registrations_signup_locations

​

registrations_signup_times

​

registrations_emergency_contacts

​

registrations_people

​

registrations_campuses

​

registrations_organizations

​

Relationship Tables

​

registrations_signup_relationships

• category - Links to registrations_categories
• campus - Links to registrations_campuses
• signup_location - Links to registrations_signup_locations
• signup_time - Links to registrations_signup_times

​

registrations_registration_relationships

• signup - Links to registrations_signups
• person - Links to registrations_people

​

registrations_attendee_relationships

• signup - Links to registrations_signups
• registration - Links to registrations_registrations
• emergency_contact - Links to registrations_emergency_contacts

​

System Fields

• system_status - Tracks data lifecycle:
  • transferring - Data being synced from Planning Center
  • active - Current, queryable data
  • stale - Outdated data pending removal
• tenant_organization_id - Ensures data isolation between organizations
• system_created_at - When Parable first received this record
• system_updated_at - Last sync timestamp

​

Row Level Security

1. Filter data to only show active records
2. Restrict access to the authenticated organization’s data
3. Ensure complete data isolation between tenants

​

Data Integrity Rules

1. Schema Qualification: Always use planning_center. prefix for all table references
2. Row Level Security: RLS automatically handles multi-tenancy and status filtering - do not add manual filters
3. Monetary Values: Cost and fee columns are stored in cents - divide by 100.0 for display
4. Registration Status Flags: Use booleans like archived, canceled, and waitlisted to control visibility instead of relying on system_status
5. Direct ID Columns: Core tables like registrations_signups expose direct ID columns for performance-critical joins

​

Common Mistakes to Avoid

1. Missing Schema Prefix
   • ❌ FROM registrations_signups
   • ✅ FROM planning_center.registrations_signups
2. Adding Redundant RLS Filters
   • ❌ WHERE tenant_organization_id = 1 AND system_status = 'active'
   • ✅ Trust RLS to handle this automatically
3. Joining Without Schema
   • ❌ JOIN registrations_attendees a ON ...
   • ✅ JOIN planning_center.registrations_attendees a ON ...
4. Skipping Currency Conversion
   • ❌ SELECT total_cost_cents as total_cost
   • ✅ SELECT total_cost_cents / 100.0 as total_cost

​

Performance Considerations

1. Indexes: All tables have optimized indexes on:
   • Primary keys and entity IDs
   • Join columns and foreign keys
   • Date columns for time-based queries
2. Query Optimization:
   • Always use the planning_center. schema prefix
   • RLS handles tenant and status filtering automatically
   • Filter registration status flags when relevant
   • Consider CTEs for complex aggregations
   • Use direct ID columns when available instead of relationship tables

​

Best Practices

1. Always join through relationship tables - Relationship tables capture many-to-many links between events and related entities
2. Trust RLS policies - Skip manual tenant_organization_id or system_status filters
3. Use Planning Center IDs for lookups - The *_id fields (e.g., signup_id)
4. Consider NULL values - Many fields may be NULL if not provided by Planning Center
5. Handle timestamps properly - All timestamps are stored in UTC

​

Example: Complete Event Details Query

-- Get full event details with all related data
SELECT 
    s.signup_id,
    s.name as event_name,
    s.description,
    s.open_at,
    s.close_at,
    cat.name as category,
    camp.name as campus,
    loc.name as location_name,
    loc.full_formatted_address,
    tim.starts_at as event_start,
    tim.ends_at as event_end,
    tim.all_day
FROM planning_center.registrations_signups s
-- Join category
LEFT JOIN planning_center.registrations_signup_relationships sr_cat
    ON sr_cat.signup_id = s.signup_id 
    AND sr_cat.relationship_type = 'category'
LEFT JOIN planning_center.registrations_categories cat
    ON cat.category_id = sr_cat.relationship_id
-- Join campus
LEFT JOIN planning_center.registrations_signup_relationships sr_camp
    ON sr_camp.signup_id = s.signup_id 
    AND sr_camp.relationship_type = 'campus'
LEFT JOIN planning_center.registrations_campuses camp
    ON camp.campus_id = sr_camp.relationship_id
-- Join location
LEFT JOIN planning_center.registrations_signup_relationships sr_loc
    ON sr_loc.signup_id = s.signup_id 
    AND sr_loc.relationship_type = 'signup_location'
LEFT JOIN planning_center.registrations_signup_locations loc
    ON loc.signup_location_id = sr_loc.relationship_id
-- Join time
LEFT JOIN planning_center.registrations_signup_relationships sr_tim
    ON sr_tim.signup_id = s.signup_id 
    AND sr_tim.relationship_type = 'signup_time'
LEFT JOIN planning_center.registrations_signup_times tim
    ON tim.signup_time_id = sr_tim.relationship_id
WHERE s.archived = false
ORDER BY tim.starts_at DESC;