# Add configurable list columns for funding applications

## Problem

The admin funding applications index table displayed a fixed set of columns. Different organisations have different workflows and need to see different information at a glance, and individual administrators within an organisation may have different preferences.

## How it works

The funding applications index table now uses the configurable columns system. Organisations can set default columns, and individual users can override those defaults with their own preferences.

### Available columns

* **Application** -- title with link to the detail page
* **Applicant** -- applicant organisation name
* **Funding Round** -- funding round name with link
* **Category** -- funding category
* **Submission Date** -- when the application was submitted
* **Status** -- current workflow status
* **Contract** -- associated contract (when contracts are enabled)
* **Collaborators** -- collaborator count (when collaborators are enabled)
* **Payment Status** -- paid/partially paid/unpaid (when payments are enabled)
* **Platform Verified** -- verification status (when platforms are enabled)
* Any **custom fields** configured with "display on index" enabled

### Organisation defaults

Default column selections can be configured under **Settings > View Settings**, alongside the existing funding round column settings.

### Per-user preferences

Individual users can click the column selector icon in the table header to choose which columns they see. Their selection is saved and persists across sessions, overriding the organisation defaults.


---

# 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://help.tahua.io/product-news/2026/april/add-configurable-list-columns-for-funding-applications.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.