# General

General includes settings of the subscription timeout, single sender identity, insights, comments, and native.

## 1. Subscription

Under this section, you can set the time for running the job and the threshold time to move the job to archive status.

### a) Job time out&#x20;

You can set the time out in minutes to run the scheduled job. If a job exceeds the specified time limit, the job will fail with a timeout error.

<figure><img src="/files/TEaU14jAbiT2kiDW7Pvl" alt=""><figcaption><p>Job timeout option</p></figcaption></figure>

{% hint style="info" %}
Depending upon the timeout cycle, the job runs for an additional 15 minutes
{% endhint %}

### b) Archive threshold&#x20;

Here you can specify the value after which the completed or paused schedules will be moved to the archived state.

<figure><img src="/files/aVdkMQotD1l8OmmDoklv" alt=""><figcaption><p>Active threshold option</p></figcaption></figure>

{% hint style="info" %}
You cannot edit, reuse or perform any operations on the jobs in the archived state.
{% endhint %}

## 2. General

### a) Enable single sender identity

If this option is enabled, then the emails will be sent using the pre-configured FROM email address like '<no-reply@inforiver.com>'.&#x20;

{% hint style="info" %}
This setting also applies to share reports, comment notifications, and subscription emails
{% endhint %}

<figure><img src="/files/YWOvKGnwITOX7N4bjTDO" alt=""><figcaption><p>Enable single sender identity option</p></figcaption></figure>

## 3. Insights

### a) Enable dataflow tracking in lineage

It's a backend feature. While logging, the data flow tracking in lineage will be enabled by default.&#x20;

<figure><img src="/files/G2rTRlS8ex1EzstY1mGO" alt=""><figcaption><p>Insights option</p></figcaption></figure>

## 4. Comments

### a) Enable groups in the organization users list

This option is enabled by default so that groups are added to the organization's users list. A user can mention a group or the distribution list in comments, comment digest, or email destination.&#x20;

<figure><img src="/files/zrv6EnVzFpesVTXJLGDv" alt=""><figcaption><p>Comments option</p></figcaption></figure>

## 5. Native

### a) Allow editing on native values in the visual

Enabling this option will allow editing the native values in the visual.

<figure><img src="/files/yeDAdykOQrapiOidRPmE" alt=""><figcaption><p>Native values option</p></figcaption></figure>

## 6. Configurable expiration time

Inforiver generates an access token when you login. Users would need to login again once the token expires. The token expiry time limit can be configured - the access tokens will be refreshed automatically in the backend, provided it is within the configured refresh token expiry limit.

<figure><img src="/files/iLly1C6xA5bSRiNyrqW5" alt=""><figcaption><p>Configurable expiration token</p></figcaption></figure>

In this section, we have covered the general settings. Navigate to the next chapter to learn more about the [writeback settings.](/admin-console/settings/writeback.md)


---

# Agent Instructions: 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:

```
GET https://docs.inforiver.com/admin-console/settings/general.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
