> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Settings

> Customize and change the settings of your Genow tenant.

The **Platform Settings** area in the admin panel is the central place to configure your Genow tenant - from branding and credentials to data retention, features, and email delivery.

<Note>
  Platform Settings can only be accessed and changed by **Global Admins**. More settings are continuously being moved into the admin panel to give you complete control over the platform.
</Note>

You reach every section below via <kbd>Admin Panel</kbd> → <kbd>Platform Settings</kbd> and the tab bar at the top.

***

## Appearance

Control the platform's default branding across two areas:

* **Colors** - set the **Primary** and **Secondary** color using hex values (for example `#FF6830`).
* **Logos** - upload your organisation's **Logo** (PNG, max 5 MB, recommended height 40-60 px, transparent background) and **Favicon** (PNG, max 512 KB, 16x16 or 32x32 px, square format).

<Note>
  These colors and logos apply to the platform's default appearance, not to a specific organisation you may currently be viewing.
</Note>

***

## Credentials Management

Credentials are the connection keys that allow Genow to access external data systems such as SharePoint, Google Drive, Jira, and others. In this screen, Global Admins can create, edit, and delete credentials centrally - and control which Agents and users can use them.

### Overview

The credentials overview lists all credentials on the platform in a searchable and filterable table. Unassigned credentials are always shown at the top.

Each credential shows:

| Column              | Description                                                 |
| :------------------ | :---------------------------------------------------------- |
| **Display Name**    | The name you gave the credential                            |
| **Connector**       | The data system type (e.g., SharePoint, Jira)               |
| **Assigned Agent**  | Which Agents can use this credential                        |
| **Assigned Person** | Which users can use this credential when configuring Agents |
| **Status**          | Assigned or Unassigned                                      |

Click the <kbd>+ Add Credential</kbd> button above the table to create a new credential.

### Creating and Editing Credentials

Creating and editing credentials uses the same two-step wizard. When editing, all existing values are prefilled.

<Steps>
  <Step title="Credential Details">
    Select the **connector type** from the dropdown. The form below then shows the fields specific to that connector - for example, an API token, a Client ID and Secret, or an Access Key.

    Enter a **Display Name** so you can identify this credential later.

    Secret fields (tokens, passwords) are hidden by default. Use the eye icon to reveal or hide them.

    Supported connector types include: SharePoint, Google Drive (Service Account), Google OAuth, Jira, Confluence, ServiceNow, and more.
  </Step>

  <Step title="Assignments">
    Optionally assign the credential to one or more **Agents** and/or **users**.

    * **Agent assignment** makes the credential available when configuring knowledge sources for that Agent.
    * **Person assignment** makes the credential available to specific users when they configure Agents, even if they do not have Global Admin rights.

    Assignments only control visibility and availability for use - they do not grant rights to edit or delete the credential.

    <Info>
      Credentials can be saved without any assignments. You can always add or change assignments later by editing the credential.
    </Info>
  </Step>
</Steps>

### Deleting Credentials

Use the delete action in the credential table to remove a credential. Only credentials that are no longer needed should be deleted - removing a credential that is still in use by a sync will break that connection.

### Why Centralized Credential Management?

Before this feature, credentials were configured individually per knowledge source, meaning the same credentials often had to be entered multiple times. With centralized management:

* Credentials are created once by a Global Admin and reused across multiple sources.
* Operational users (Agent admins or creators) can be given access to specific credentials without needing Global Admin rights.
* Sensitive credentials never need to be shared directly with non-admin users.

***

## Data Retention & Compliance

Configure after how many days data is automatically deleted. For each data type you can choose **No automatic deletion**, **30**, **60**, or **90 days**:

* **Conversation Retention Period**
* **Personalized Feedback Retention Period**
* **Anonymous Feedback Retention Period**
* **Analytics Retention Period**
* **User Activity Retention Period**

<Warning>
  Automatic deletion is permanent and applies platform-wide. Changes take effect the next day.
</Warning>

***

## Network & Connectivity

A **Network Connectivity Debugging** tool lets you test whether the platform can reach a specific service. Enter the protocol (e.g. TCP), host, port, and a timeout, then run the test. This is helpful when setting up connectors or diagnosing firewall and network issues.

***

## LLM & Pipeline Settings

Provides an overview of the language models currently in use on your platform. There are no editable settings in this section at the moment.

***

## Service Accounts

Manage the platform and API service accounts used for automation and programmatic access to Genow.

***

## QR Code Access

A global switch that controls whether QR code access links can be created for Agents at all. When **Enable QR code access globally** is turned off, no QR codes can be generated on any Agent - even for Agent Admins who hold the required permission.

<Card title="QR-Code Agent Access" icon="qrcode" horizontal href="/use-case-management/settings/qr-code-access">
  Learn how Agent Admins create QR codes and access links for individual Agents.
</Card>

***

## Translator Glossary

Found under the **Features** tab, the **Translator Glossary** lets you control how specific terms are translated across the platform. This is useful for product names, internal abbreviations, or any terms that should either be translated in a specific way or left untranslated entirely.

### How It Works

* Upload a CSV file that maps source terms to target terms.
* When the source and target term are the same, the translator will pass that term through untranslated.
* The glossary applies to all translation usage across the platform - there is one global glossary for all Agents.
* Only one glossary can be active at a time. Uploading a new file replaces the existing one.
* You can download a CSV template directly from the settings screen to see the required format with examples.
* To remove the glossary, delete it from the settings screen. The translator will then fall back to its default behaviour.

<Note>
  Agent-specific glossaries are not supported at this time. The uploaded glossary applies platform-wide.
</Note>

***

## API Documentation

Browse the interactive API documentation for each backend service - **Core API**, **Search API**, and **PDF Converter API**. The documentation reflects the exact version deployed in your environment, and you can download the OpenAPI spec for each service.

***

## Third-Party Notices

The **Third-Party Notices** section lists all open-source packages and external libraries used by the Genow platform, together with their version and license. This supports your organisation's software compliance and license management. The list is updated automatically from dependency scans.

***

## SMTP Email

Configure an SMTP server for outbound email delivery. The sender address you set up here is used for platform notifications. At the moment, the platform sends a notification when a chat is shared with a user.

You can add, edit, test, or delete an SMTP server entry from this screen.