# Editing an Organisation

To modify the setup details of an organisation, including its modules, after deployment, follow these steps to access and update the organisation configuration:

{% hint style="info" %}
**Important:** Anyone can propose changes or updates to an organisation’s setup. However, only the multi-signature (multi-sig) wallet owners have the authority to review, sign, and approve these proposed changes. Once the required approval threshold is met, an additional step is required: the “execute transaction.” This final transaction, which implements the approved changes, can be triggered by anyone.
{% endhint %}

### 1. Navigate to the Organisations Menu

On the left sidebar, click on the Organisations menu. This will take you to a page displaying a list of all available organisations.

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2FTcoCnaieImO53dwuttEC%2FScreenshot%202025-01-26%20at%2018.38.16.png?alt=media&#x26;token=ca5af597-1578-4c36-8aea-d427f7bf8838" alt=""><figcaption></figcaption></figure>

### 2. Locate the Organisation to Edit

Scroll through the list or use the search bar at the top to find the specific organisation you wish to edit. Once located, click on the Explore button associated with that organisation.

### 3. Access the Edit Modules Option

On the organisation’s details page, locate and click the Edit Modules button. This will allow you to access the module configuration settings.

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2FTjNxjORgtaEgsGZrJtkX%2FScreenshot%202025-01-26%20at%2019.10.10.png?alt=media&#x26;token=9f602c28-ae2e-491a-9401-aca57966dfbf" alt=""><figcaption></figcaption></figure>

### 4. Follow On-Screen Instructions

After clicking Edit Modules, follow the on-screen settings and instructions to make the desired changes on the modules. You can add new modules, remove unused ones [(see 4.1)](#id-4.1-removing-unused-modules), or adjust existing configurations as needed.

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2F72Y4EUmRFJ8Y2RDpEFoq%2FScreenshot%202025-01-07%20at%2019.19.05.png?alt=media&#x26;token=82a8d1cd-ab34-4767-ae05-f3008f6fbfe5" alt=""><figcaption><p>Modules cannot be deselected directly on the Module Selection page. However, they can be removed in subsequent steps.</p></figcaption></figure>

#### 4.1 Removing unused modules

Modules cannot be deselected directly on the Module Selection page. However, they can be removed in subsequent steps if necessary. Specifically, the Working Group and Safe Treasury modules can be removed if they are not actively used by the organisation.

To remove these modules:

1\. Click Continue to proceed to the Module Configuration page.

2\. Locate the module you wish to remove and click the trash bin icon to delete the unwanted module from the configuration.

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2FZfOwZowaTXiPMEt4niIX%2FScreenshot%202025-01-07%20at%2019.20.04.png?alt=media&#x26;token=3abecfdb-5487-4015-bb8f-95f1038978d1" alt=""><figcaption></figcaption></figure>

### 5. Save Changes

Once all updates have been made, ensure you save and deploy the changes as per the instructions provided within the module configuration flow.

***

### **Now it’s time to approve the deployed changes by signing the proposal.**

To proceed, follow the steps outlined in the [**Wizard | Protocol Upgrades page**](https://docs.lucidlabs.fi/modules-and-integrations/wizard-or-protocol-upgrades) or below:

### Navigate to the “Wizard” module (listed as “Protocol Upgrades” in the module grid). Here, you will see the pending proposal you just created and deployed. Now the proposal has to be signed.

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2Fk7pn5fvJuuz9JlL9aJDb%2FScreenshot%202025-05-27%20at%2012.18.55.png?alt=media&#x26;token=32de9e77-2b4b-456c-8108-63efe0d45347" alt=""><figcaption></figcaption></figure>

You will see:

* Proposal Name and Date
* Threshold required (e.g., 1/1, 2/3)
* Current number of collected signatures

<figure><img src="https://1245019432-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWTLxE0cK05dkLTY4VPzs%2Fuploads%2FMJ9vdnmPvGDqPreecN1Q%2FScreenshot%202025-05-27%20at%2012.23.21.png?alt=media&#x26;token=70faa9f5-2408-4b02-8ee7-fc27f70632b5" alt=""><figcaption></figcaption></figure>

Click “**View**” to review the changes in detail.

Then click “**Sign**” to approve.

Once enough signatures are collected based on the threshold, the organisation update goes live.

{% hint style="info" %}

* Any community member can submit suggestions for upgrades and save them with a specific proposal name. However, only approved multi-sig signers can approve them
* Only individuals with multi-sig approval authority can sign and approve the proposed upgrade.
* If the required approval threshold is met, the upgrade is automatically executed. It can upgrade contracts, UI elements and more.
* Proposals that are not executed immediately remain in the Proposal History section for future review and action.
  {% endhint %}
