> For the complete documentation index, see [llms.txt](https://docs.bitbadges.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitbadges.io/other-modules/x-managersplitter/messages/msg-create-manager-splitter.md).

# MsgCreateManagerSplitter

## Overview

`MsgCreateManagerSplitter` creates a new Manager Splitter entity with specified permissions. The manager splitter receives a module-derived address that can be used as a collection manager.

## Message Structure

```protobuf
message MsgCreateManagerSplitter {
  option (cosmos.msg.v1.signer) = "admin";
  option (amino.name) = "managersplitter/CreateManagerSplitter";

  // Admin address creating the entity.
  string admin = 1;

  // Permissions mapping each CollectionPermission field to execution criteria.
  ManagerSplitterPermissions permissions = 2;
}
```

## Fields

### `admin` (string, required)

The address that will be the permanent admin of the manager splitter. This address:

* Has full control over the manager splitter
* Can always execute all permissions
* Can update and delete the manager splitter
* Cannot be changed after creation

Must be a valid Bech32 address.

### `permissions` (ManagerSplitterPermissions, optional)

The permissions configuration for the manager splitter. Each permission maps to `PermissionCriteria` that specifies which addresses can execute that permission.

If `nil` or not provided, an empty permissions structure is created (all permissions denied except for admin).

## ManagerSplitterPermissions Structure

```protobuf
message ManagerSplitterPermissions {
  PermissionCriteria canDeleteCollection = 1;
  PermissionCriteria canArchiveCollection = 2;
  PermissionCriteria canUpdateStandards = 3;
  PermissionCriteria canUpdateCustomData = 4;
  PermissionCriteria canUpdateManager = 5;
  PermissionCriteria canUpdateCollectionMetadata = 6;
  PermissionCriteria canUpdateValidTokenIds = 7;
  PermissionCriteria canUpdateTokenMetadata = 8;
  PermissionCriteria canUpdateCollectionApprovals = 9;
}
```

Each field is optional. If a permission is not set, it is denied by default (except for the admin).

## PermissionCriteria Structure

```protobuf
message PermissionCriteria {
  // List of approved addresses that can execute this permission.
  repeated string approvedAddresses = 1;
}
```

### `approvedAddresses` (string\[], optional)

A list of Bech32 addresses that are approved to execute this permission. If empty, only the admin can execute this permission.

## Response

```protobuf
message MsgCreateManagerSplitterResponse {
  // The address of the created manager splitter.
  string address = 1;
}
```

### `address` (string)

The module-derived address of the created manager splitter. This address:

* Is deterministic based on the manager splitter ID
* Can be used as a collection manager address
* Is derived using `ModuleAddress(ModuleName, ID_bytes)`

## Validation

The message is validated to ensure:

1. The `admin` address is a valid Bech32 address
2. The manager splitter address doesn't already exist (shouldn't happen, but checked for safety)

## State Changes

1. A new Manager Splitter entity is created with:
   * A module-derived address (based on next available ID)
   * The specified admin address
   * The specified permissions (or empty if not provided)
2. The next manager splitter ID is incremented

## Usage Example

```json
{
  "admin": "bb1...",
  "permissions": {
    "canUpdateCollectionMetadata": {
      "approvedAddresses": [
        "bb1abc..."
      ]
    },
    "canUpdateTokenMetadata": {
      "approvedAddresses": [
        "bb1def456..."
      ]
    },
    "canUpdateValidTokenIds": {
      "approvedAddresses": []
    }
  }
}
```


---

# 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.bitbadges.io/other-modules/x-managersplitter/messages/msg-create-manager-splitter.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.