wip

jhrv · jhrv · commit eebbc209dfd5 · 2024-02-06T09:05:57.000+01:00
diff --git a/docs/explanation/nais-teams.md b/docs/explanation/nais-teams.md
diff --git a/docs/explanation/observability/logging.md b/docs/explanation/observability/logging.md
@@ -115,7 +115,7 @@ Enheter i Nav som skal ha tilgang: <four digit department code>. E.g (2990 - IT-
 
 ### 2 Connect the AD group to your team in Kibana
 
-The logs your apps produces are linked with your [nais-team](../nais-teams.md).
+The logs your apps produces are linked with your [nais-team](../team.md).
 Administrators of Kibana will create a role for your team with read rights to those logs.
 Whoever is in the AD-group (created in step 1) will get the Kibana role, and can thus read all logs produced by apps belonging to the nais-team.
 
diff --git a/docs/explanation/team.md b/docs/explanation/team.md
@@ -0,0 +1,50 @@
+# Team
+
+Everything in NAIS is organized around the concept of a team.
+
+A team is a group of people, typically working on the same set of products or services, and sharing the same set of responsibilities. 
+
+The team owns the workloads built by the team, as well as all provisioned resources. Nothing is owned by an individual, but by the team as a whole. This is to ensure that the team can continue to operate even if a member leaves the team.
+
+A team doesn't necessarily map directly to the organizational team unit, and usually consists of technical people involved in the actual development and operations. The reason for this is that being member of a NAIS team will grant you access to all the workloads and provisioned resources that the team owns. To reduce the attack surface, it's a good idea to limit access to the people that actually need it.
+
+## The anatomy of a team
+
+A team has two different roles, `owner` and `member`. 
+A team has at least one `owner`, and can have multiple `members`. The `owners` have permission to add and remove `members`, as well changing the roles of the `members`.
+You can be a member and owner of multiple teams.
+
+## What does NAIS provide a team?
+
+When you [create a team](../how-to/create-team.md), NAIS will ensure you have the following:
+
+- A isolated area for your team's workload, in each environment (e.g. dev and prod)
+- A GitHub team with the same name, in your GitHub organization. The members of your NAIS team will be synchronized with the GitHub team.
+
+
+TODO:
+- Requirement: google user
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/how-to-guides/create-team.md b/docs/how-to-guides/create-team.md
@@ -2,19 +2,18 @@
 
 This how-to guide shows you how to create a NAIS team.
 
-!!! note 
-    Creating a team comes with quite a bit of overhead so this excersise should only be completeted if you are not part of a relevant team and just want find your bearings and get started.
-
-## Prerequisites
+## 0. Prerequisites
 - [naisdevice installed](./naisdevice/install-naisdevice.md)
 - A GitHub Account with access to your org. (eg. navikt) 
 - A Slack channel that can receive alerts concerning your apps and workloads
 
-### 1. Create your team
+## 1. Create your team
 
-1. Open [NAIS Teams](https://console.<<tenant()>>.cloud.nais.io/) in your browser and autenticate with your credentials.
+1. Open [Console](https://console.<<tenant()>>.cloud.nais.io/) in your browser, and autenticate.
 2. Click on "Create" 
 3. Choose a team name, add a description of the team and the Slack channel that is mentioned in the prerequisites.
 4. Click "Create"
 
-Your team will now be created and the needed resources on which to run your workloads.
+Your team will now be created, and you will be the owner. 
+
+Read more about what resources are created for your team [here](../explanation/team.md).
diff --git a/docs/how-to-guides/workload-crud-operations.md b/docs/how-to-guides/workload-crud-operations.md
@@ -4,7 +4,7 @@ This guide shows you how to perform CRUD-operations on your workload.
 
 ## 0. Prerequisites
 - [Command-line access to the cluster](./command-line-access.md)
-- [Member of a NAIS team](../explanation/nais-teams.md)
+- [Member of a NAIS team](../explanation/team.md)
 - [Workload spec](../explanation/workloads.md)
 
 === "Application"
diff --git a/docs/tutorial/hello-nais/hello-nais-1.md b/docs/tutorial/hello-nais/hello-nais-1.md
@@ -6,7 +6,7 @@ This tutorial will take you through the process of getting a simple node applica
 
 - You have a GitHub account connected to your GitHub organization (e.g. `navikt`)
 - [naisdevice installed](../../how-to-guides/naisdevice/install-naisdevice.md)
-- [Member of a NAIS team](../../explanation/nais-teams.md)
+- [Member of a NAIS team](../../explanation/team.md)
 - [GitHub CLI installed](https://cli.github.com/)
 
 ???+ note "Conventions"
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -114,7 +114,7 @@
 #          - Tracing: explanation/observability/tracing.md
 #          - Alerts: explanation/observability/alerts.md
 #          - Logs: explanation/observability/logs.md
-#      - NAIS Teams: explanation/nais-teams.md
+#      - NAIS Teams: explanation/team.md
 #      - Kafka: explanation/kafka.md
 #      - Persistent Volume Storage: explanation/persistent-volume-storage.md
 #      - Database:
