# Manage your project

Project settings have different permissions. The artist address, team membership and contract ownership are separate roles; owning an edition does not grant project administration rights.

## Publication and minting

A project starts inactive and paused. A team member controls **active** status. The artist or a team member can toggle **paused**. Public minting requires active, unpaused status, an available edition and payment of at least the project price. The artist and team bypass active/paused restrictions, but not the price or edition cap.

The deployed entry point is `anyoneMintProjectEdition(projectId)`, one edition per call. It does not include built-in batch, allowlist, per-wallet allocation, or randomness-reveal arguments. Do not confuse a future gate design with a feature of that entry point.

Send the intended mint price. The full `msg.value` is forwarded to the royalty manager; this method does not refund an overpayment.

## Artist or team settings

The artist or a team member can change price, grid size, pause state and image URL configuration. While the project is unlocked they can also change its name, artist display name, description, maximum editions, script transaction reference and script type.

The edition cap cannot be lower than editions already minted and cannot exceed the contract limit of 1,000,000. The display grid size is a separate setting and does not change the edition supply.

Changing a script reference can change how already-minted editions render. Review and preserve the old reference, and communicate changes rather than treating a reference update as a harmless text edit.

## Artist-only settings

The current artist can update the artist address and the additional payee information. Use the platform's project settings so the parent project and its royalty manager stay coordinated. Changing only the manager directly can leave the parent project's artist mapping out of sync.

Check a new recipient address carefully. Changing the artist address transfers the platform's artist authority; changing the additional payee changes payment distribution. See [sales and royalties](/docs/royalties) for how existing balances are treated.

## What locking means

`artistTeamLockProject` blocks the contract's `onlyUnlocked` fields: project name, artist name, description, max editions, script transaction reference and script type.

It does **not** freeze price, pause, image URLs, grid size, artist address or additional-payee settings. The contract owner can unlock a project with `contractOwnerUnlockProject`. Describe this precisely to collectors; it is not an irreversible renunciation of every permission.

The deployed Solidity itself remains immutable reference code in this repository. Changing settings through its functions and changing the contract implementation are different things.

## A release check

Confirm the project ID, exact script-post transaction, renderer, price, supply limit, active/paused state, artist wallet and payout recipients. Test a live edition, then confirm the intended lock state. Inspect transaction receipts before retrying a failed-looking action: a slow interface is not proof that a transaction failed.

Source basis: `ImmutablesAdminProject` and `ImmutablesArt` in the [deployed art contract source](https://etherscan.io/address/0xA8A6CB3978e2c4EdcF5A3d0cB3400E1E5D031479#code), and the frontend's `ProjectAdminModal` / `BlockchainWriteProvider`.