anchor.diff:  ---
   ## <a name="builder-origin" id="builder-origin" data-magellan-target="builder-origin">Origins</a>
   
  -An origin is a place on Chef Habitat Builder where you can store, share, and build packages. It is a unique namespace within Builder, and while you can delete or transfer an origin, you can't rename an origin after it is created. One example of an origin is the "core" origin, which is the set of foundational packages managed and versioned by the core Chef Habitat maintainers.
  +An origin is a place on Chef Habitat Builder where you can store, share, and build packages. It is a unique namespace within Chef Habitat Builder, and while you can delete or transfer an origin, you can't rename an origin after it is created. One example of an origin is the "core" origin, which is the set of foundational packages managed and versioned by the core Chef Habitat maintainers.
   
   You can join existing origins by invitation and you can create your own origins.
   For more on invitations, see [origin membership and RBAC](/#origin-members).
  
positive.code: | Transfer Origin | N | N | N | N | Y |
  | Delete Origin | N | N | N | N | Y |
  
  ### Manage Origin Membership in Builder
  
  In tandem with the changes to the Builder membership roles, we've also updated the `hab` CLI to support RBAC. We're working on adding role management to the Chef Habitat Builder site, but in the meantime, you'll need to use the CLI for now.
  
  
negative.code: 
  The Chef Habitat SaaS builder offers additional functionality including Automated Builds,
  
  For more information on how the SaaS and On-Prem versions of Chef Habitat Builder work together, read the blog - [Chef Habitat Builder On-Prem Enhancements that Extend Support to Airgap Environments and Simplify Set-Up](https://blog.chef.io/chef-habitat-product-announcement-builder-on-prem-enhancements-that-extend-support-to-airgap-environments-and-simplify-set-up/)
  
  ## Compare Chef Habitat Builder and Builder on-prem
  
  