---
description: >-
  This page can be found within each pipe. To access this page, enter your pipe
  and click on the Gear icon on the top right corner of the page.
---

# Pipe settings

<details>

<summary>Collaborators (coming soon!)</summary>

Coming soon!

</details>

<details>

<summary>Transfer Pipe</summary>

### Step 1: Making the transfer

1. Enter the email address you wish to transfer the pipe to. (**They'll have to login at least once for this feature to work.)**
2. Click on "Transfer Pipe".
3. Click on "Yes, transfer pipe" if the email address has been entered correctly.
4. A message indicating the pipe has been transferred will be shown (screenshot below).

<figure><img src="https://2212031742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXyVsBiX9OwOL1o9g5hLM%2Fuploads%2FwPcbGHItp2z7U6FUZRWp%2Fimage.png?alt=media&#x26;token=de5df2b0-f19a-4eed-8ae0-9ac94db52ad3" alt=""><figcaption></figcaption></figure>

Your pipe is now pending transfer. Get your colleague to double check the pipe connections and actions.

* You will need to **manually pass over the permissions and credentials** for each connection involved e.g. **FormSG** would involve you handing ownership or editor rights of the form to the receiving user and passing of the secret key as well. **M365 excel** will require the receiving user to be granted the right permissions and access to the file involved.

- If you accidentally made a transfer request to the wrong user, you can click on "cancel" to retract it.

* The process is only completed once your colleague accepts the pipe transfer on their account.

### Step 2: Accepting a Pipe transfer

1. Receiving user will need to login to [Plumber](https://plumber.gov.sg/) and accept the transfer.
2.  A prompt will appear on the receiver's account as seen in the screenshot below.\


    <figure><img src="https://2212031742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXyVsBiX9OwOL1o9g5hLM%2Fuploads%2F0P3PPuWmH1SDSNiC0FI7%2Fimage.png?alt=media&#x26;token=1fba1750-248a-4595-b399-d2e3a8f52966" alt=""><figcaption></figcaption></figure>

3) Click on "View and accept".

4. You'll be brought to another page to accept or reject the trasnfer.
5. Ensure that you reconnect all connections and check all steps in the pipe to ensure that everything works well. If there are no connections involved, you should be able to immediately publish the pipe and it will still work as intended.

</details>

<details>

<summary>Email notifications</summary>

<figure><img src="https://2212031742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXyVsBiX9OwOL1o9g5hLM%2Fuploads%2Fs2YGitMw5i4wiLqV9582%2Fimage.png?alt=media&#x26;token=21b6a351-f413-4b41-bc2e-274fad7191bc" alt=""><figcaption></figcaption></figure>

This is where you customise the frequency of receiving error notifications from us. Choose from these options:

| Option                                                   |                                                                                                                                                                |
| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| First error on this pipe, one email notification per day | When the first error on your pipe for that day is detected, we send an email to you. No emails will be sent for subsequent errors that happen on the same day. |
| Each error on this pipe                                  | Whenever there is an error, we send an email to you. For e.g. 100 errors = 100 emails                                                                          |

</details>





