> 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/user-documentation/registration-and-personal-settings/email-signature.md).
# Email Signature
This lesson will show you how to create an email signature in AgileCase.
### Accessing email signature
Email signatures allow you to create your own automated sign off for your emails. To access email signatures, click the "E-Mail Signature" button under "Personal" on the settings menu.
### Create an email signature
On this page you can create your email signature by entering text in the text box. Clicking "Enable Signature" will apply this signature to any emails you create.
### Edit HTML view
By clicking the pencil button, you can edit the HTML of your signature to add hyperlinks. The syntax ` (linked text) ` will generate a hyperlink to the specified URL. Once you have finished composing your signature, click the "Save Changes" button to save this as your email signature.
### Signature on an email
After creating a signature, it will automatically be populated in any email you compose in the system.
---
# 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/user-documentation/registration-and-personal-settings/email-signature.md?ask=&goal=
```
`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.