> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/permanent-teams-6182619.md).

# Permanent teams

**Setting up Permanent Teams**

It is possible to set up *Permanent Teams* in JobManager. This is used if employees often or allways work together on Projects or machines.

(however, teams can also be accessed in Registration cockpit/client, without setting up permanent teams, if used only infrequently)

There will be a Pilot (responsible) and one or more assistants. The assistants choose to access the Pilot and then the Pilot will be the one to choose (start/stop) jobs.

ONLY assistants can resign from a team. The Pilot however can choose another employee for the role as Pilot, and then be able to resign.

The table *Permnent Teams* contains the teams that are stored in JobManager.

Stored teams can be restarted later. They are set up [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-4).

[Pilot](#field-1)\
[Assistant](#field-2)\
[Active](#field-5)\\

## See also

## Reference

\
\\

<details>

<summary>Pilot</summary>

Employee No. of the associated pilot.

</details>

<details>

<summary>Assistant</summary>

Employee No. for the assistant.

</details>

<details>

<summary>Active</summary>

Indicates whether the line is active, and therefore included.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/permanent-teams-6182619.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
