> For the complete documentation index, see [llms.txt](https://docs.skydeck.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skydeck.ai/da/control-center/setup-guide/organize-teams.md).

# Organiser Teams

I SkyDeck.AI Control Center er tags en måde at organisere medlemmerne af din virksomhed på. Et tag (eller gruppe) repræsenterer et team inden for din organisation. Du kan tildele et tag til et medlem eller et værktøj, og medlemmer kan kun bruge værktøjer, der er tildelt det samme tag.

Vælg **Organiser** fra sidepanelet. Fra denne side kan du oprette tags for at definere og strukturere forskellige teams inden for din organisation. Du vil bemærke, at **Alle** tag allerede eksisterer og ikke kan fjernes. Dette er det standard tag, der gælder for alle medlemmer af din organisation.

<figure><img src="/files/uhMnojyFpKCZGDcAxKVf" alt="default all tag"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.skydeck.ai/da/control-center/setup-guide/organize-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
