> 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 Review 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 Review 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 Review 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.<br>

Just select the appropriate Field–Value pairs to ensure the task is reviewed with the right policy context.

<figure><img src="https://2804394160-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD9Htw9DUg294GuYmAyyj%2Fuploads%2Fgit-blob-eaa48e82ccf7c38c3a21bc1eafea921427ab79de%2Ftask-attributes.jpg?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.tryprotege.com/review/review-tool-concepts/brands-and-attributes/use-in-tasks.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.
