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

# Organization Management

The Organization Management page allows you to manage your organization's settings, team members, and various AWS Partner-related configurations. This guide will walk you through the main sections and their functionalities.

## Organization Settings

This section contains your basic organization information and settings. Note that only administrators and owners have permission to modify organization settings.

### Organization Details

* **Organization Name**: Your company's name as it appears in the system
* **Description**: A detailed description of your organization, including your specializations, services, and key focus areas

## Model Routing

By default Darcy runs inference on its own managed models. This section lets you point your organization at your own AWS account instead, so model usage is billed to you. Only administrators and owners can see or change it.

Two options are available, and only one can be active at a time:

* **AWS Bedrock Mantle**: The recommended option. Deploy a CloudFormation template to create a Bedrock project in your AWS account, connect it with a scoped API key, then choose which model powers each of Darcy's **Smart**, **Fast**, and **Analytical** tiers. See [AWS Bedrock Mantle](/build/integration-overview/aws/bedrock-mantle-integration.md).
* **AWS Bedrock**: The earlier integration, using IAM access keys. Models are fixed rather than selectable. See [AWS Bedrock Integration](/build/integration-overview/aws/aws-bedrock-integration.md).

## AWS Partner Settings

AWS Partner configuration is no longer edited here. This page links to it, and the settings themselves live in the **AWS Partner Settings** panel on the **Partners Hub** and **AWS ACE Dashboard** headers — next to the opportunities they govern. Only administrators and owners can change them.

What's in that panel:

1. **Automated PO Identification**
   * Turn automatic Partner Originated opportunity identification on or off
   * Choose the ACE solutions used for default submissions
   * Decide whether submissions go to AWS automatically or are left as drafts
2. **APFP Funding**
   * Enable the AWS Partner Funding Program and assign funding programs to your organization
3. **WAFR Creator**
   * Automated creation and management of AWS Well-Architected Framework Reviews. Requires MontyCloud
4. **AWS Marketplace**
   * Enable AWS Marketplace product and offer management

See [AWS ACE](/partner/ace-dashboard.md) for what these settings affect day to day.

## Document Templates

This section allows you to manage document templates for your organization. Only administrators and owners can upload or delete templates.

### Template Management

* Upload document templates (DOCX, PPTX) for organization-wide use
* Templates are available to all organization members
* Supported file types: Documents and Presentations

### Example Templates Includes:

Open a provided Template Example to see how to customize a Template to interact with DarcyIQ

Templates Provided:

* Word Docx Template
* Powerpoint PPT Template

## Organization Members

This section displays and manages your organization's team members.

### Member Management Features

* Search functionality to find specific members
* Filter members by role
* View active members list
* Member information displayed:
  * Name
  * Email
  * Role


---

# 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.darcyiq.com/settings-and-configuration/organization-management.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.