When creating a Flow Process in Membrain, one of the key configuration steps is selecting a Parent Type. This setting determines what kind of entity the Flow is tied to - and helps ensure the workflow is properly connected within your CRM environment.
There are four Parent Types to choose from:
The selected Parent Type determines what data is available inside a Flow Project.
Each Flow Project can access process fields, along with fields tied to its Parent Type. For example, a Company Flow can use company data, while a Contact Flow can use contact data.
Graphs inside Flows follow the same principle. Data is scoped to what is directly connected to the Flow Project.
For project-based graphs, data is limited to records linked through relationship fields. Contact-based graphs reflect stakeholders added to the Flow. Activity and document data are scoped to what exists within the Flow Project itself.
Because of this, relationship fields play an important role when building reports inside Flows. If data is not connected, it will not appear in graphs.
Choose this when your Flow is related to an organization rather than a specific person.
It ensures everyone interacting with a company has visibility into shared processes and responsibilities, reducing handover issues and missed steps.
Flow Projects with a Company Parent Type have access to process fields, company fields, and stakeholder-related data.
When using graphs inside a Flow, the data is scoped to records that are directly connected to the Flow Project through relationship fields. This means that if you want to report on related projects, contacts, or other data, those connections must exist within the Flow Project.
This is the right option when the process focuses on an individual person - typically a prospect, buyer, or stakeholder.
It keeps workflows personal and targeted, ensuring your actions stay aligned with an individual's role.
Flow Projects with a Contact Parent Type have access to process fields, contact fields, and stakeholder-related data.
Graphs based on contacts are scoped to stakeholders added to the Flow Project. This ensures that reporting reflects only the individuals directly involved in that specific workflow.
Use this type when the Flow is tied to an internal team member - typically to support individual routines or responsibilities.
It helps team members stay organized and consistent in their day-to-day work, even outside of sales opportunities.
Flow Projects with a User Parent Type have access to process fields and user-related data.
Because these Flows are tied to internal users, available data is limited to what is connected to that user and the Flow Project itself. Graphs and reporting will reflect only this scoped data.
For Flow Processes with the User Parent Type, a setting in the Process Settings allows you to automatically grant view access to the assigned Parent User.
When the Grant Access to Parent User toggle is enabled, the Parent User is automatically able to view the Flow Project they are responsible for. This toggle is available for all Flows with a Parent Type of User, and it is enabled by default for newly created Flow Processes of this kind.
With this setting active, the Parent User does not need to be manually added to the project to gain access. This feature simplifies access management and ensures that responsible team members always have visibility into their assigned Flows.
If your workflow doesn’t need to be tied to a specific entity, select “None.” This is useful for general-purpose Flows or templates.
It gives you the flexibility to create repeatable structures that are reused across different contexts or teams.
Flow Projects without a Parent Type only have access to process fields by default.
If you need to connect additional data, such as companies or contacts, this must be done using relationship fields. Graphs and reporting will only include data that has been explicitly connected to the Flow Project.
Selecting the right Parent Type ensures your Flow connects to the right data and fits naturally into your workflow.
Each Parent Type determines what the Flow is centered around, whether that’s a company, contact, user, or no specific entity. This affects where the Flow appears in Membrain and who is expected to work within it.
When deciding which Parent Type to use, focus on ownership and intent. Ask yourself who the process belongs to and who needs visibility into it. A company-level process is typically shared across a team, while a contact or user Flow is more focused and specific.
For additional support feel free to reach out to your Membrain contact or contact support@membrain.com
