mirror of
https://github.com/coder/coder.git
synced 2026-11-07 21:29:37 +08:00
d04eaf8392
- [x] Mention Orgs is beta and add a link to get feedback - [x] Add docs on new provisioner authentication architecture and deprecate the old one - [x] Add/update docs for IdP sync - [x] Organization Sync - [x] Group Sync - [x] Role Sync - [x] Modify `coder.com` codebase to add `Premium` and `Beta` pill, and allow multiple pills: https://github.com/coder/coder.com/pull/638 - [x] Replace all mentions of "Enterprise" with "Premium" in docs - [x] edit: change it to "Licensing" - [x] Remove the enterprise page and change all links to coder.com/pricing - [x] Merge #14786 - [x] Add redirects for coder.com to redirect the `using-organizations` guide to the new orgs one and /enterprise to /premium https://github.com/coder/coder.com/pull/645 - [x] Custom roles - [x] https://github.com/coder/coder/pull/14786 - [x] Remove all mentions of orgs experiment - [x] Update in-product copy & links to link to the new docs pages Anything I am missing? --- [Preview this](https://coder.com/docs/@orgs-licenses/admin/organizations) --------- Co-authored-by: Edward Angert <EdwardAngert@users.noreply.github.com> Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com> Co-authored-by: Jaayden Halko <jaayden.halko@gmail.com>
111 lines
3.8 KiB
Markdown
111 lines
3.8 KiB
Markdown
# Organizations (Premium)
|
|
|
|
> Note: Organizations requires a [Premium license](../licensing.md). For more
|
|
> details, [contact your account team](https://coder.com/contact).
|
|
|
|
Organizations can be used to segment and isolate resources inside a Coder
|
|
deployment for different user groups or projects.
|
|
|
|
## Example
|
|
|
|
Here is an example of how one could use organizations to run a Coder deployment
|
|
with multiple platform teams, all with unique resources:
|
|
|
|
|
|
|
|
## The default organization
|
|
|
|
All Coder deployments start with one organization called `Coder`.
|
|
|
|
To edit the organization details, navigate to `Deployment -> Organizations` in
|
|
the top bar:
|
|
|
|
|
|
|
|
From there, you can manage the name, icon, description, users, and groups:
|
|
|
|
|
|
|
|
## Additional organizations
|
|
|
|
Any additional organizations have unique admins, users, templates, provisioners,
|
|
groups, and workspaces. Each organization must have at least one
|
|
[provisioner](./provisioners.md) as the built-in provisioner only applies to the
|
|
default organization.
|
|
|
|
You can configure [organization/role/group sync](./auth.md) from your identity
|
|
provider to avoid manually assigning users to organizations.
|
|
|
|
## Creating an organization
|
|
|
|
### Prerequisites
|
|
|
|
- Coder v2.16+ deployment with Premium license with Organizations enabled
|
|
([contact your account team](https://coder.com/contact)) for more details.
|
|
- User with `Owner` role
|
|
|
|
### 1. Create the organization
|
|
|
|
Within the sidebar, click `New organization` to create an organization. In this
|
|
example, we'll create the `data-platform` org.
|
|
|
|
|
|
|
|
From there, let's deploy a provisioner and template for this organization.
|
|
|
|
### 2. Deploy a provisioner
|
|
|
|
[Provisioners](../admin/provisioners.md) are organization-scoped and are
|
|
responsible for executing Terraform/OpenTofu to provision the infrastructure for
|
|
workspaces and testing templates. Before creating templates, we must deploy at
|
|
least one provisioner as the built-in provisioners are scoped to the default
|
|
organization.
|
|
|
|
Using Coder CLI, run the following command to create a key that will be used to
|
|
authenticate the provisioner:
|
|
|
|
```sh
|
|
coder provisioner keys create data-cluster-key --org data-platform
|
|
Successfully created provisioner key data-cluster! Save this authentication token, it will not be shown again.
|
|
|
|
< key omitted >
|
|
```
|
|
|
|
Next, start the provisioner with the key on your desired platform. In this
|
|
example, we'll start it using the Coder CLI on a host with Docker. For
|
|
instructions on using other platforms like Kubernetes, see our
|
|
[provisioner documentation](../admin/provisioners.md).
|
|
|
|
```sh
|
|
export CODER_URL=https://<your-coder-url>
|
|
export CODER_PROVISIONER_DAEMON_KEY=<key>
|
|
coder provisionerd start --org <org-name>
|
|
```
|
|
|
|
### 3. Create a template
|
|
|
|
Once you've started a provisioner, you can create a template. You'll notice the
|
|
"Create Template" screen now has an organization dropdown:
|
|
|
|
|
|
|
|
### 5. Add members
|
|
|
|
Navigate to `Deployment->Organizations` to add members to your organization.
|
|
Once added, they will be able to see the organization-specific templates.
|
|
|
|
|
|
|
|
### 6. Create a workspace
|
|
|
|
Now, users in the data platform organization will see the templates related to
|
|
their organization. Users can be in multiple organizations.
|
|
|
|
|
|
|
|
## Beta
|
|
|
|
Organizations is in beta. If you encounter any issues, please
|
|
[file an issue](https://github.com/coder/coder/issues/new) or contact your
|
|
account team.
|