> For the complete documentation index, see [llms.txt](https://docs.rara.social/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rara.social/implementation/permissions.md). # Permissions The RaRa protocol is managed via a permission system implemented in the AddressManager.sol contract. This allows specified addresses on the chain to take administrative actions. These include: * Updating contract implementations * Updating parameters (such as the price of 1 reaction) * Updating protocol addresses * Updating the default Bonding Curve implementation * Others It should be noted that there is some risk associated with upgradeable contracts and parameter management, but in no way can anyone or any contract involved in the protocol take ownership of your NFTs or move them in any manner. To use the protocol, you only prove ownership of an NFT at registration and do not give any approvals to the protocol for the NFT or move the NFT in any protocol owned contracts or addresses. #### Administrative Multisig The protocol is currently managed via a 2-of-4 Gnosis multisig wallet by the team. This will ensure multiple parties are responsible for managing any changes to the protocol and allow multiple confirmations from different members before any changes go into effect. --- # 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.rara.social/implementation/permissions.md?ask=&goal= ``` `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.