> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/product-docs/contributing/feature-page-template.md).

# Feature page template

## Feature page template

> Copy this file to `features/<area>/<feature-slug>.md` (or `features/<feature-slug>.md` if there is no obvious area yet) and fill in the sections below. Delete this preamble in the copy.
>
> **Length guidance:** aim for one screen of skimmable content per section. If a section grows past a few paragraphs, consider splitting it into a sub-page and linking from here. The catalogue earns its keep by being scannable — long-form deep dives belong on the concept pages.

***

## {{ Feature name }}

*One or two sentences: what this feature is, and which problem it solves.*

### For users

* **Where it lives.** Sidebar entry, URL, or workflow entry-point.
* **When to use it.** The trigger / pain it addresses.
* **How to use it.** The happy-path walkthrough — concise steps, screenshots if helpful.
* **What it gives you.** Outputs, exports, side-effects in the UI.

### For implementers

* **Surface area.** Backend models / Django app touched, frontend routes added, API endpoints exposed.
* **Key integration points.** What other features depend on this one. What it depends on.
* **Gotchas.** Anything surprising — permission rules, ordering, folder scoping, race conditions, library shape, migration concerns.
* **Configuration.** Feature flags, environment variables, library entries needed.

### Status

* **Shipped in:** commit / version / release tag
* **Owner:** team or person
* **Feature flag:** if applicable, name and default state
* **Edition:** community / enterprise / both

### Related

* Links to relevant concept pages, sibling features, or external standards.


---

# 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://intuitem.gitbook.io/ciso-assistant/product-docs/contributing/feature-page-template.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.