--- updatedAt: 2026-10-09T22:30:00.000Z --- # Branches Branches allow you to segment People along geographic boundaries using custom-drawn shapes on a map. Branches are on the Professional and Enterprise plans. For example, "Rideshare Drivers United - Los Angeles" may contain several branches representing different parts of the city (Central LA, East LA, South LA, Orange County, etc.). Branches can be created at two levels: * **Chapter-level branches** - Segment people within a specific Chapter * **Organization-level branches** segment people across an Organization. The root Organization and each sub-organization can have their own branches. When a Person's location is set, they are automatically assigned to the appropriate Branch based on their postal code or address. ## Multiple Branch Memberships A Person can belong to multiple branches simultaneously—one branch per scope (Chapter or Organization) they belong to. For example, if someone belongs to both "LA Chapter" and the root Organization, they could be assigned to: * "East LA" branch (from the LA Chapter) * "Southern California Region" branch (from the Organization) This allows for flexible geographic segmentation at different organizational levels. *** # Drawing Boundaries Team Members with permission can create and modify branch boundaries from **Settings > Branches**. Use the scope selector at the top to choose which Chapter or Organization you're managing branches for. To create a new Branch: 1. Click **Edit** at the top of the map. Then click **Draw branch**. 2. Click to place each corner of the boundary. Click the starting point to finish. 3. When you finish the shape, the **Add Branch** window opens. 4. Type the **Branch Name**. Click **Submit**. ![](https://files.readme.io/d14cea3-branches.png "branches.png") To update an existing Branch, click 'Edit' on the map, click the branch, and drag its points. Then click 'Save' on the branch row. *** # Bulk Upload via GeoJSON For organizations with many branches, uploading a GeoJSON file is faster than drawing each boundary manually. 1. **Prepare your file** - Create a GeoJSON file with `Polygon` or `MultiPolygon` features. Each feature becomes a branch. 2. In the info box above the map, click the 'bulk upload a GeoJSON file' link. 3. Upload your `.geojson` file 4. Check the number of branches and the branch names, then click 'Upload Branches'. Common sources for boundary files: * Census tract, block group, and state legislative district boundaries from census.gov. Convert them to GeoJSON before you upload them. * Custom boundaries that you draw in [geojson.io](https://geojson.io) > 💡 **Tip**: If your source data is in Shapefile format, convert it to GeoJSON before you upload it. In QGIS, right-click the layer and select **Export ► Save Features As…**, then select the GeoJSON format. ### MultiPolygon Support Branches support both simple `Polygon` and complex `MultiPolygon` geometries. This is useful for non-contiguous regions (like island territories or districts with disconnected areas). *** # Branch Assignment Logic The system assigns a branch in each scope (Chapter or Organization) the Person belongs to. A Person inside overlapping branches in one scope gets only one of them. *** # Branch Details Each branch can be customized with specific details and used in automations to streamline task assignment and coordination. ### Editable Branch Details | Setting | Description | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Branch Name** | The display name for the branch (e.g., "Orange County") | | **Color** | The branch shows in this color on the map and in the branch table. | | **Branch Captain** | A Team Member who serves as the captain for this branch. Used in automations to route follow-up tasks or manage branch-specific activities | | **Sync to Chapter** | When enabled, users assigned to this branch are automatically added to the selected Chapter. Useful for Organization-level branches that should also grant Chapter membership | | **Require within bounds** | When it is on, only people inside the shape get this branch. When it is off, the branch can also get people who are inside no branch. | ![](https://files.readme.io/77efb72f9204e010537fd0d3146d6a75b9c809bbba55fb47b7878150d179bf76-image.png) *** # Sync to Chapter The **Sync to Chapter** feature adds people in the branch to the Chapter that you select. It works on Organization-level branches and on Chapter-level branches that sync to a different Chapter. *** # Using Branches in Automations Branches integrate with automations in several ways: ### Branch Captain Assignment In the 'Assign agent' or 'Add follow-up task' action, choose 'Branch Captain (if available)'. ### Filtering by Branch When building automation conditions or user filters, you can filter People by their branch membership. *** # Branch Merge Tags Use these merge tags in emails, texts, and pages: | Tag | Output | | --------------------- | ------------------------------------------------------------------------ | | `{{ user.branch }}` | The Person's branch name for the current scope | | `{{ user.branches }}` | A comma-separated list of the Person's branch names in the sending scope | ### Scope-Aware Behavior Both tags depend on the scope that sends the message, such as the blast, automation, event, or page. They show only the Person's branches in that scope and in the Chapters under it.