> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/types-of-custom-field/username-in-table-control.md).

# Username in Table Control

Username fields take on a different functionality when used in a custom field table. This lesson explains the difference.

### Username field in a custom field table

<figure><img src="/files/QJGpSlv3AcJCIMTlhKtk" alt="" width="131"><figcaption></figcaption></figure>

When creating a custom field table, username fields are generated in exactly the same way as usual but function slightly differently in the table itself. The column in the screenshot shows a username field in a custom field table.

The user stamp is now automated, so the name of the user that makes the entry is listed without having to click a button.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agilecase.com/administrator-documentation/types-of-custom-field/username-in-table-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
