anchor.diff:  Get-ChildItem C:\hab\cache\keys
   ```
   
  -On Linux or MacOS:
  +On Linux or macOS:
   
   ```bash
   ls -la /hab/cache/keys
  
positive.code: * Public packages are visible in search results and can be used by every Chef Habitat Builder user
  * Private artifacts do not appear in search results and are available only to users with origin membership
  
  Change the default setting for the origin by switching from **Public artifacts** to **Private artifact**. The default setting required for each origin and users with more than one origin can set some as public and others as private. Packages can have different default visibility settings than their origin's. Change the default visibility setting in for individual packages in that package's setting tab (Builder > Origin > Package > Settings).
  
  ### <a name="origin-secrets" id="origin-secrets" data-magellan-target="origin-secrets">Origin Secrets</a>
  
  Everyone with origin membership can view origin secrets, but only origin administrators and owners can add, update, or delete settings. located on the bottom of the _Settings_ tab (Builder > Origin > Settings > "Origin Secrets") let you encrypt and store secrets as environment variables. Origin secrets are useful for plans that require access to protected resources at build time, such as private source-code repositories and cloud storage providers.
  
  Origin secrets are retained by the origin and are available for any of that origin's packages. The origin secrets in your local environment are encrypted with an origin encryption key. Only Chef Habitat Builder can read encrypted origin secrets.
  
  
negative.code: ### Manage Member Roles with `hab rbac`
  
  You can use role based access control (RBAC) from the command line.
  An origin `MEMBER_ACCOUNT` is the name used to sign in to Chef Habitat builder. You can find the list of user names on an origin's _Members Tab_. (Builder > Origin > Members)
  
  The RBAC command syntax is:
  
  