​

Planning Center Groups Data Model

​

Overview

​

Visual Data Model

​

Core Entity Relationships

​

Key Relationships Explained

• GROUP_TYPE categorizes groups (small groups, classes, teams, etc.)
• GROUPs are organized by type with flexible hierarchies
• MEMBERSHIPs link people to groups with roles (member, leader, owner)

• ENROLLMENT tracks join requests and approvals
• Separate from MEMBERSHIP to handle pending/requested states
• Once approved, becomes an active MEMBERSHIP

• Groups host EVENTs (meetings, activities, gatherings)
• ATTENDANCE tracks who actually attended
• RSVPs track who plans to attend
• EVENT_NOTEs provide additional context

• Location association via groups_group_relationships (relationship_type: location)
• Campus linkage via groups_group_relationships (relationship_type: campus)
• Resource assignments via groups_group_relationships

• TAG_GROUPs organize related tags
• TAGs enable flexible categorization across groups
• Applied 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)

​

Core Tables Overview

​

Primary Entity Tables

• groups_groups - Small groups, classes, and teams
• groups_people - People who can join groups
• groups_memberships - Connections between people and groups
• groups_events - Group meetings and gatherings
• groups_attendances - Event attendance records
• groups_rsvps - Event RSVP responses from group members
• groups_group_types - Categories for organizing groups
• groups_locations - Physical meeting places
• groups_enrollments - Sign-up and registration management

​

Supporting Entity Tables

• groups_campuses - Campus locations
• groups_campus_groups - Links between campuses and groups
• groups_event_notes - Notes for events
• groups_group_applications - Applications to join groups
• groups_organizations - Organization settings
• groups_owners - Group ownership information
• groups_resources - Group resources
• groups_tags - Labels for group characteristics
• groups_tag_groups - Tag groupings

​

Relationship Tables

• groups_group_relationships - Links groups to other entities
• groups_membership_relationships - Links memberships to related entities
• groups_event_relationships - Links events to related entities
• groups_attendance_relationships - Links attendances to related entities
• groups_rsvp_relationships - Links RSVPs to events, groups, and people
• groups_enrollment_relationships - Links enrollments to related entities
• groups_group_application_relationships - Links applications to related entities

​

Table Definitions

​

groups_groups

​

groups_people

​

groups_memberships

​

groups_events

​

groups_attendances

​

groups_rsvps

​

groups_group_types

​

groups_locations

​

groups_enrollments

​

groups_tags

​

groups_tag_groups

​

groups_campuses

​

groups_group_applications

​

groups_event_notes

​

groups_organizations

​

groups_owners

​

groups_resources

​

groups_campus_groups

​

Relationship Tables

​

groups_group_relationships

• GroupType - Links to groups_group_types
• Location - Links to groups_locations
• Tag - Links to groups_tags
• Enrollment - Links to groups_enrollments
• Campus - Links to groups_campuses

​

groups_membership_relationships

​

groups_event_relationships

• Group - Links to groups_groups
• Location - Links to groups_locations

​

groups_attendance_relationships

• Event - Links to groups_events
• Person - Links to groups_people

​

groups_rsvp_relationships

• Event - Links to groups_events
• Group - Links to groups_groups
• Person - Links to groups_people

​

groups_enrollment_relationships

​

System Fields

• tenant_organization_id - Multi-tenant organization identifier
• system_status - Data lifecycle status:
  • transferring - Being imported from Planning Center
  • active - Current active data
  • stale - Marked for removal
• system_created_at - When record was created in Parable
• system_updated_at - When record was last updated in Parable

​

Common Query Patterns

​

Finding a Person’s Groups

SELECT
    g.name as group_name,
    g.description,
    m.role,
    m.joined_at
FROM planning_center.groups_memberships m
JOIN planning_center.groups_groups g
    ON m.group_id = g.group_id
WHERE m.person_id = 'PERSON_ID'
    AND g.archived_at IS NULL
ORDER BY m.joined_at DESC;

​

Getting Group Members with Roles

SELECT
    g.name as group_name,
    p.first_name,
    p.last_name,
    m.role,
    m.joined_at
FROM planning_center.groups_groups g
JOIN planning_center.groups_memberships m
    ON g.group_id = m.group_id
JOIN planning_center.groups_people p
    ON m.person_id = p.person_id
WHERE g.group_id = 'GROUP_ID'
ORDER BY m.role DESC, m.joined_at;

​

Finding Events for a Group

SELECT
    e.name as event_name,
    e.starts_at,
    e.ends_at,
    e.location_type_preference,
    e.canceled
FROM planning_center.groups_events e
JOIN planning_center.groups_event_relationships er
    ON e.event_id = er.event_id
    AND er.relationship_type = 'Group'
WHERE er.relationship_id = 'GROUP_ID'
    AND e.starts_at >= CURRENT_DATE
ORDER BY e.starts_at;

​

Tracking Event Attendance

SELECT
    e.name as event_name,
    e.starts_at,
    COUNT(CASE WHEN a.attended = true THEN 1 END) as attended_count,
    COUNT(DISTINCT ar.relationship_id) as total_invited
FROM planning_center.groups_events e
LEFT JOIN planning_center.groups_attendance_relationships ar
    ON e.event_id = ar.relationship_id
    AND ar.relationship_type = 'Event'
LEFT JOIN planning_center.groups_attendances a
    ON ar.attendance_id = a.attendance_id
GROUP BY e.event_id, e.name, e.starts_at
ORDER BY e.starts_at DESC;

​

Event RSVPs Summary

SELECT
    e.name as event_name,
    e.starts_at,
    COUNT(CASE WHEN r.response = 'yes' THEN 1 END) as yes_count,
    COUNT(CASE WHEN r.response = 'no' THEN 1 END) as no_count,
    COUNT(CASE WHEN r.response = 'maybe' THEN 1 END) as maybe_count,
    COUNT(*) as total_rsvps
FROM planning_center.groups_events e
JOIN planning_center.groups_rsvp_relationships er
    ON e.event_id = er.relationship_id
    AND er.relationship_type = 'Event'
JOIN planning_center.groups_rsvps r
    ON er.rsvp_id = r.rsvp_id
WHERE e.starts_at >= CURRENT_DATE
GROUP BY e.event_id, e.name, e.starts_at
ORDER BY e.starts_at;

​

Finding RSVPs for a Person

SELECT
    e.name as event_name,
    e.starts_at,
    g.name as group_name,
    r.response
FROM planning_center.groups_rsvps r
JOIN planning_center.groups_rsvp_relationships er
    ON r.rsvp_id = er.rsvp_id
    AND er.relationship_type = 'Event'
JOIN planning_center.groups_events e
    ON er.relationship_id = e.event_id
JOIN planning_center.groups_rsvp_relationships gr
    ON r.rsvp_id = gr.rsvp_id
    AND gr.relationship_type = 'Group'
JOIN planning_center.groups_groups g
    ON gr.relationship_id = g.group_id
JOIN planning_center.groups_rsvp_relationships pr
    ON r.rsvp_id = pr.rsvp_id
    AND pr.relationship_type = 'Person'
WHERE pr.relationship_id = 'PERSON_ID'
    AND e.starts_at >= CURRENT_DATE
ORDER BY e.starts_at;

​

Groups by Type

SELECT
    gt.name as group_type,
    COUNT(DISTINCT g.group_id) as group_count,
    SUM(g.memberships_count) as total_members
FROM planning_center.groups_group_types gt
LEFT JOIN planning_center.groups_group_relationships gr
    ON gt.group_type_id = gr.relationship_id
    AND gr.relationship_type = 'GroupType'
LEFT JOIN planning_center.groups_groups g
    ON gr.group_id = g.group_id
    AND g.archived_at IS NULL
GROUP BY gt.group_type_id, gt.name
ORDER BY gt.position;

​

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: Group event fees or donations stored in cents should be divided by 100.0 for display
4. Archived Groups: Use archived_at IS NULL or archived_at comparisons to control visibility instead of checking system_status
5. Direct ID Columns: Core tables such as groups_groups and groups_memberships expose direct IDs for performance-sensitive joins

​

Common Mistakes to Avoid

1. Missing Schema Prefix
   • ❌ FROM groups_groups
   • ✅ FROM planning_center.groups_groups
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 groups_memberships m ON ...
   • ✅ JOIN planning_center.groups_memberships m ON ...
4. Skipping Currency Conversion
   • ❌ SELECT suggested_donation_cents as suggested_donation
   • ✅ SELECT suggested_donation_cents / 100.0 as suggested_donation

​

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 archived groups or attendance flags when relevant
   • Consider CTEs for complex multi-join queries
   • Use direct ID columns when available instead of relationship tables

​

Data Types and Conventions

​

Location Preferences

• physical - In-person meetings
• virtual - Online meetings
• hybrid - Both in-person and online

​

Roles

• member - Regular group member
• leader - Group leader with additional permissions

​

RSVP Responses

• yes - Person plans to attend
• no - Person will not attend
• maybe - Person is undecided

​

Application Status

• pending - Awaiting review
• approved - Accepted into group
• rejected - Not accepted

​

Next Steps

• Return to Overview for high-level understanding
• Review Basic Queries for simple examples
• Check Advanced Queries for complex analysis
• See Reporting Examples for production-ready reports