> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/detailed-flows/detailed-admin-functions-flow.md).

# Detailed Admin Functions Flow

Transfer ownership, pause/unpause contracts, manage token approvals, and securely move locked NFTs cross-chain via Ethereum.

* As the contract Owner, you have full administrative rights for your personal CryptoLegacy contract.
* **Ownership Transfer:**
  * Transfer contract ownership anytime by sending a transaction for each contract on each chain.
* **Pause Contract:**
  * Pause the contract at any time, preventing asset withdrawals from your main wallets.
  * Optionally, remove token approvals during this state.
* **Unpause Contract:**
  * Unpause the contract anytime.
  * After unpausing, update the timeout if necessary by sending another transaction.
* **NFT Transfer on Ethereum:**
  * Transfer your locked NFT on Ethereum anytime by sending a single transaction.
* **NFT Transfer on Other Chains:**
  * To transfer a locked NFT on another chain:
    1. Switch to Ethereum and send a transaction to update the locked NFT owner, propagating the update via deBridge.
    2. Wait for bridge confirmations.
    3. Switch to the target chain and send a transaction to confirm the transfer.


---

# 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.cryptolegacy.app/detailed-flows/detailed-admin-functions-flow.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.