Introduce a new guide for managing organizations under a Coderdeployment. This document provides step-by-step instructions forsetting up and utilizing organizations to segment and isolateresources for different user groups or projects.Changes:- Added `organizations.md` guide in `docs/admin`- Renamed and relocated relevant images to `docs/images/admin/organizations`- Updated `manifest.json` to include the new organizations guide- Removed the obsolete "Using Organizations" guideThis change facilitates better organization of the admindocumentation and aligns with the introduction of enterprisefeatures requiring a premium license.

Switch the icon for the organizations guide to provide bettervisual representation and consistency with other documentation.- Use "orgs.svg" instead of "group.svg" for the organizations guide.

- Changed the `state` of the RBAC documentation entry in `manifest.json`  to an array allowing for multiple states.- Added "beta" as an additional state alongside "enterprise" to  highlight that this feature is also in beta testing.

Organizations is in beta. If you encounter any issues, please- [file an issue](https://github.com/coder/coder/issues/new)- Contact your account teamRemove outdated using-organizations guideThis guide was outdated and redundant with the more comprehensivedocumentation found in the admin section.

Remove references to the now-deleted enterprise page across variousdocs. New URL points directly to the pricing page.- Removed enterprise links from docs- Updated enterprise links to point directly to pricing page

- Emphasize benefits of running external provisioners.- Update authentication information with detailed steps and examples.- Reorganize and clarify the types and scopes of provisioners.- Provide detailed example commands and common use cases for each type.- Enhance security guidance and best practices.```sh- Improved explanations of the types and scopes of provisioners- Added commands for creating and authenticating provisioners- Provided step-by-step instructions for running provisioners- Updated examples for Kubernetes, Docker, and VM setupsProvisioners are now easier to understand and configure, especially with new scoped key options and user token examples. This ensures better security and operational efficiency.

- Change "enterprise" references to "premium" to reflect the new branding.- Ensure consistency across various documentation sections.- Update relevant links and terms for clarity.### Changes:- Appearance section title updated to include premium.- SCIM, Group Sync, Role Sync, and multiple other sections retitled for premium.- FAQs and guides updated to reflect new premium terminology.- Manifest JSON entries updated to list "premium" alongside "enterprise".- Networking and port forwarding documentation updated to include premium.- Added user quiet hours and autostop requirement sections updated to indicate premium.- Ensure all references in various docs are consistent with the new premium branding.

- Improve directions and clarity for enabling group sync- Introduce new licensing guide for setting up premium featuresChanges:- Detailed steps and examples added for configuring OIDC claims- New `licensing.md` guide presents ways to add a license via UI and CLI- Introduced new enterprise SVG icon for better visual representationThese updates aim to enhance the user experience and provide clear, actionable instructions.

adds new feature sections### To do- [x] populate or delete scope of support sections   - [ ] if populate, then:      - what should people expect      - how/where do they get it- [x] rm Alpha?- [ ] ~link to wikipedia?~- ~EA:<https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha>~- ~Experimental:<https://en.wikipedia.org/wiki/Software_release_life_cycle#Feature-complete>~- ~Beta:<https://en.wikipedia.org/wiki/Software_release_life_cycle#Open_and_closed_beta>~---------Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>

To provide clarity on where to find the user's OIDC groups and roles,instructions were added to check both `id_token_claims` and`user_info_claims`.Enhanced examples include exact steps:- How to use group IDs for configuring synchronization.- Mapping multiple groups for `coder-admins` and `coder-users`.Updated details:- Differentiated between `group-sync` and `role-sync` settings.- Added a prompt for using premium licenses for organization-level sync.New UI screenshots for added clarity:- Added `group-sync.png` and `role-sync.png` for visual guidance.

- Deleted submodules 'asdsadas' and 'data-takehome'.- Improved JSON formatting for clarity.- Refined UI text for better guidance on creating provisioners.

Correct the path to the licensing document in the organizations guide to ensure proper navigation for users.

- Refine description to include "Premium" in feature availability.- Adjust terminology in auth and sync sections for consistency.- Modify organization documentation to reflect unified naming.

- Remove outdated reference to free usage.- Add link to new Premium plan blog post for existing customers.

Clarified sentences by combining related information, making it easier to understand the options for exploring Premium features.

stirby left a comment

Switch the `state` property in documentation manifest entries fromsingle strings to arrays across all relevant fields for consistency.This aligns the JSON structure, allowing multiple states to be clearlydefined when necessary and ensures future flexibility in state assignments.