> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/brands-and-attributes/use-in-tasks.md).
# Use in Tasks
### 🔄 Auto-Detecting and Editing Attributes from External Platforms
When a Task is scanned from an integrated platform like Jira or Asana, Protege AI will automatically attempt to detect and assign Attributes based on the content of the ticket.
#### 🧠 Automatic Detection
If your task's description includes recognizable values that match your configured Attributes (e.g., marketing channel, region, or product), Protege AI will auto-populate those values during the scan setup.
For example:
* If a Jira ticket includes the phrase “For use in CA for sportsbook” Protege AI may assign:
* state = CA
* product = sportsbook
#### ✏️ Manual Reassignment
If:
* No attributes were detected, or
* You want to override or refine the detected values,
You can do so in the Attributes section of the Content Scanner Job setup.
Just select the appropriate Field–Value pairs to ensure the task is reviewed with the right policy context.
---
# 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.tryprotege.com/review/review-tool-concepts/brands-and-attributes/use-in-tasks.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.