Orgs is an enterprise feature. We should ensure it is effectively and coherently gated prior to releasing as an experiment.

Requirements

• experiment name should be appropriate and documented
• add small notice if experiment is enabled but user does not have premium license
• make sure org features cannot be accessed and orgs cannot be created without a premium license
• change site-wide permissions to be org-scoped where necessary in line withthis PR
• ensure that the UI doesn't error for single-org deployment after we've added all these new org features
• add Jest tests for above cases
• Organization sidebar settings should be conditional based on actor's capabilities.
  • "Organization Settings" should change to "Organization Summary" if the user cannotorganization.<org_id>.update
  • Seecomment below for conditionalideas
• Docs link for orgs/premium license
• Update middleware error to say premium instead of enterprise
• Show summary if not entitled

Known issues

• groups page user dropdown shows all users on the site, not just members of the organizatinon. When adding a user to the group if they are not in the org, you get an error "User must be a member of organization "rabbit-group""