> 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/employee-activate-6182317.md).

# Employee Activate

Indicates the periods where the employee is active.

An active employee can register transasactions and is counted as part of the total licensed number of employees.

| Topic                 |
| --------------------- |
| [Employee](#field-1)  |
| [From Date](#field-4) |
| [To Date](#field-5)   |
| [Only IPC](#field-10) |

## See also

[License for JobManager](https://docs.dynalogic.com/birds-jobmanager-product-overview/getting-started/licensing.md)

## Reference

\
\\

<details>

<summary>Employee</summary>

No. of the related Employee.

</details>

<details>

<summary>From Date</summary>

Date from where the line starts.

</details>

<details>

<summary>To Date</summary>

Date to where the line ends.

</details>

<details>

<summary>Only IPC</summary>

This field indicates that the employee is only used for simple time registration during this activation.

There is a special type of license for these employees.

The Employee is limited to only registering *Absence*, *Trigger* and one *IPC*. The *one* IPC is specified in the field [Only IPC (Job Id)](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md#field-300) on the [JobManager Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md) table.

**Related topics**

* [JobManager Setup](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-setup-6182300.md)

</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/employee-activate-6182317.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.
