> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/setting-up-meeting-notetaker.md).

# Setting Up Meeting Notetaker

### Overview

Meeting Notetaker requires Account-level enablement and correct permissions.

Setup focuses on capture inputs, output storage, and access control.

### Key Concepts

* **Enablement**: feature availability at Account scope
* **Capture permissions**: microphone and recording permissions (browser and policy dependent)
* **Output scope**: which Organization and Project the meeting belongs to
* **Retention**: how long meeting records remain available (plan dependent)

### How It’s Used

Complete setup once per Account.

Revisit setup when access models or retention policies change.

### Benefits

* Consistent meeting capture across delivery teams
* Faster creation of requirements and tasks from discussion
* Better auditability through traceable meeting sources

### Setup Steps

{% stepper %}
{% step %}

### Confirm feature availability

1. Confirm Meeting Notetaker is enabled for the Account.
2. Confirm the intended Organization and Project scopes exist.
   {% endstep %}

{% step %}

### Configure permissions and capture inputs

1. Allow microphone access for the Transform domain.
2. Confirm browser settings allow audio capture when required.

Related: [Browser Compatibility](/getting-started/browser-compatibility.md)
{% endstep %}

{% step %}

### Validate access to outputs

1. Confirm Teammate access is correct at Organization and Project scope.
2. Confirm meeting outputs are visible to the intended roles.

Related: [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Use least-privilege access for meeting content.
* Capture governance meetings consistently to build continuity.
* Standardize naming for Projects and meetings for easier retrieval.

### Summary

Setup requires feature enablement, capture permissions, and correct access scope.


---

# 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://help.transform.ai/ai/setting-up-meeting-notetaker.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.