> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/picturethis/configuration/configuration-screen/label.md).

# Label

#### Header Align

In table view, change the alignment of headers, giving your data a polished and organised look. Whether it’s left, center, or right alignment, easily customize your tables to suit your needs.

#### Text Align

In Table view you generally want to align your text to the left (or right when in an RTL region) while Cards view often looks best when text is centred in the Label of the Cards. This option allows you to set the alignment of the text in your card or Table cell by choosing Left, Centre or Right.

#### Font size

Use the dropdown to change size of the font. Min size 6pt, max size 24pt.

#### Tableau & Google fonts

When you change the font of your workbook, PictureThis will incorporate that font in to the extension to match your dashboards style. Tableau and Google fonts can be used.

#### Font Family

Now added – Google Fonts! Enable google fonts to your font library. Change the font from the dropdown to improve the look of your dashboard and match your corporate identity.

<br>


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/picturethis/configuration/configuration-screen/label.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.