How Filtering by OrganizationNode Works

How Filtering by OrganizationNode Works



Imagine you are looking for specific project memberships in an organization. These memberships can be directly connected to a part of the organization, but sometimes they are linked indirectly through the project, the role type, or the person assigned to the membership.
Here’s how we figure out if a project membership belongs to an organization:
    First Check: Direct ConnectionThink of this as asking, "Does this membership itself explicitly belong to a specific organization I’m looking for?"
  • If the project membership has a direct link to the organization, it’s a match. This direct connection is done in the 'Edit project membership' modal.
    Second Check: Indirect ConnectionIf the membership doesn’t have a direct connection (the organization field = empty), we check the entities it is related to:
  • The project: Does the project this membership belongs to connect to an organization in the BASIC INFO tab?
  • The role: Is the type of role (such as "Architect", "Developer", etc.) tied to an organization in the ADMIN → ROLES view?
  • The person: Is the person assigned to this membership connected to an organization in that person's BASIC INFO tab?
→ If any of these connections (direct or indirect) match, we include the membership in the results.