> For the complete documentation index, see [llms.txt](https://guide.plumber.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.plumber.gov.sg/who-are-you-building-for.md).

# Who are you building for?

Before you build a pipe, think about who will own it and look after it in the long run. Some actions in Plumber connect to apps that are tied to the person who set them up. Planning for this at the start saves a lot of rework later, for example when the pipe needs to be handed over to someone else.

Pick the situation closest to yours:

* [Building for myself](#building-for-myself)
* [Building for someone else](#building-for-someone-else)
* [Building for a team](#building-for-a-team)
* [Building for a large-scale campaign](#building-for-a-large-scale-campaign)

***

### Building for myself

This is the simplest setup. You own the pipe, and every connection in it (Slack, Telegram, Ownself Gather, M365 Excel) is set up under your account.

Things to keep in mind:

* If you might change roles or leave your agency while the pipe is still in use, read [Building for someone else](#building-for-someone-else) first. It's much easier to set the pipe up under the right person from the start than to move it later.
* Add a colleague as a collaborator, so someone else can view or edit the pipe if you're away.

***

### Building for someone else

If you're building a pipe that another person will own or run day to day, build it under **their** account from the start, especially if the pipe uses any of these actions:

| Action             | What happens when the pipe changes owner                                                                                                                                                                                                                                                                    |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Slack**          | The Slack steps keep working, but they still use the Slack app (bot) created by the original owner.                                                                                                                                                                                                         |
| **Telegram**       | The Telegram steps keep working, but they still use the bot token generated for the original owner through @BotFather.                                                                                                                                                                                      |
| **Ownself Gather** | The Ownself Gather steps keep working, but they still use the original owner's API key and its permissions.                                                                                                                                                                                                 |
| **M365 Excel**     | **The Excel steps stop working.** Excel files live in the owner's own Plumber folder in SharePoint, and that folder can't be transferred. The new owner has to connect M365 Excel on their account, recreate the Excel file (same tables and columns) in their own folder, and point each Excel step to it. |

For Slack, Telegram and Ownself Gather, the pipe keeps running on the original owner's app, bot or API key after the handover. If anything goes wrong with it later, for example the key is revoked or the bot is removed, the new owner has to sort it out with the original owner, who may have already left the organisation. Until it's sorted out, or the new owner sets up their own connections, those steps won't work.

**The best way to start:** create the pipe, and all the connections above, under the account of the person who will own the pipe for the long run. You can still help build it by being added as a collaborator on their pipe.

If a pipe does need to change owners later, use **Transfer pipe**, or [contact us](https://guide.plumber.gov.sg/help/contact-us.md) if the current owner has left. Expect to reconnect the actions above after the transfer.

***

### Building for a team

If a pipe is used by a team rather than one person:

* **Add your teammates as collaborators** so more than one person can view or edit the pipe, and the pipe isn't stuck if one person is away or leaves.
* **Using a group email is fine**, both as a recipient and as a Plumber account your team logs in with. Make sure the group mailbox is set up to **receive emails from the internet**. Plumber's emails, including login codes and Email by Postman notifications, are sent from outside the government network, so a mailbox that only accepts internal emails won't receive them. If you're unsure, check with your agency's IT team.
* **Group emails can't use M365 Excel.** In the government's Microsoft 365 setup, a Plumber Excel folder can only belong to one individual, not to a group or shared mailbox. If your team's pipe needs Excel, connect it from one person's account, or use Tiles instead.

***

### Building for a large-scale campaign

If your pipe will handle a lot of submissions in a short time, such as a nationwide registration or a public campaign, here's what to know:

* **Our highest load so far:** NDP ticket balloting, with more than 300,000 submissions over a month and more than 36,000 in the busiest single hour. That's what we consider nationwide scale. For that event we raised our limits ahead of time.
* **Below that scale, you're very likely fine.** For example, 3,000 to 5,000 submissions an hour doesn't need anything special on our side.
* **Submissions are queued, not dropped.** If many come in at once, Plumber works through all of them, but not necessarily in the order they were submitted.
* **M365 Excel will lag behind at high volume.** Plumber still processes every submission, but at high volume it can take some time before new rows show up in your Excel file. This is a limitation on the Excel side that we can't speed up. If your campaign needs data to appear in Excel quickly, that isn't possible, so plan your process around the delay.
* **Add collaborators** so more than one person can monitor the pipe and retry failed runs during the campaign.
* **Planning something nationwide?** [Contact us](https://guide.plumber.gov.sg/help/contact-us.md) before launch so we can check whether anything needs to be adjusted for your event.
