Q: What is "Parent Record Owner" in workflow notifications?
A: Parent Record Owner refers to the user assigned to the parent record in a 1:many relationship structure within Dazos CRM.
When you select this option in a workflow's internal notification settings, the notification goes to whoever is assigned to the parent record, not the individual record that triggered the workflow.
Q: How does Parent Record Owner work in practice?
A: Here's a step-by-step example using the common 1 Account : multiple Intake Opportunities relationship:
Setup: Account "ABC Company" is assigned to Sarah Johnson
Child Records: Multiple Intake Opportunities exist under ABC Company, each potentially assigned to different users
Workflow Trigger: An Intake Opportunity under ABC Company triggers your workflow
Notification Result: Sarah Johnson receives the internal notification because she's assigned to the parent Account record
This happens regardless of who is assigned to the individual Intake Opportunity that triggered the workflow.
Q: What are common examples of parent-child relationships in Dazos?
A: Common 1:many relationship structures include:
1 Account : multiple Intake Opportunities
1 Account : multiple Leads
1 Lead : multiple Activities
1 Contact : multiple Call Logs
In each case, selecting "Parent Record Owner" sends notifications to whoever is assigned to the "1" side of the relationship.
Q: When should I use Parent Record Owner vs. other notification options?
A: Use Parent Record Owner when:
You want to notify the account manager or primary relationship owner
Child record activities should alert the parent record's responsible party
You need notifications to go to a consistent person regardless of who handles individual child records
Use other options like "Record Owner" when you want to notify the person assigned to the specific record that triggered the workflow.
Q: What if Parent Record Owner notifications aren't working as expected?
A: Verify the following:
Confirm the parent record has someone assigned in its "Assigned To" field
Check that your workflow is targeting the correct child module
Ensure the parent-child relationship is properly configured in your CRM
Test with a known parent-child record pair to confirm the relationship structure
Related Resources
How to Create CRM Workflows Triggered by Task Completion
How to Set Up Workflow Conditions for Multiple Options (All vs Any Conditions)
Troubleshooting Workflow Email Delivery Issues