# Rallly
**Schedule group meetings, without the back-and-forth**
[**Website**](https://rallly.co) · [**Documentation**](https://support.rallly.co) · [**Discord**](https://discord.gg/uzg4ZcHbuM)
[](https://github.com/lukevella/rallly/actions)
[](https://crowdin.com/project/rallly)
[](https://www.gnu.org/licenses/agpl-3.0)
[](https://discord.gg/uzg4ZcHbuM)
[](https://www.paypal.com/donate/?hosted_button_id=7QXP2CUBLY88E)
Rallly is an open-source scheduling tool that helps you find the best date and time to meet. Create a poll with a few options, share the link, and let your participants vote on when they're available. No more back-and-forth emails.
## ✨ Features
- 📅 **Date & time polls** — Propose multiple options and find what works for everyone
- 🗳️ **No account needed to vote** — Participants just open the link and respond
- 📊 **Availability grid** — See everyone's responses at a glance
- 💬 **Comments** — Discuss the details right on the poll
- 🔔 **Notifications** — Get notified when participants respond
- ✅ **Finalize a date** — Pick the winning option and notify everyone
- 🌍 **10+ languages** — Community-translated via [Crowdin](https://crowdin.com/project/rallly)
- 🔒 **Open source & self-hostable** — Own your data
## ☁️ Cloud version
The quickest way to get started is the hosted version. Create your first poll in seconds, no installation required.
**[Try Rallly free →](https://rallly.co)**
## 🐳 Self-hosting
Prefer to run your own instance? Rallly ships as a Docker image and can be self-hosted in minutes.
See the [self-hosting docs](https://support.rallly.co/self-hosting) for installation and [configuration options](https://support.rallly.co/self-hosting/configuration-options).
## 🛠️ Built with
[Next.js](https://github.com/vercel/next.js/) · [Prisma](https://github.com/prisma/prisma) · [tRPC](https://github.com/trpc/trpc) · [TailwindCSS](https://github.com/tailwindlabs/tailwindcss)
## 🤝 Contributing
Contributions are welcome! Have a look at the [contributing guide](CONTRIBUTING.md) to get started with local development and find out how you can help.
- 🌐 **Translators** — Help [translate Rallly](https://support.rallly.co/contribute/translations) into your language
- 🔐 **Security** — Found a vulnerability? See our [security policy](SECURITY.md)
- 🤝 **Community** — Please read our [Code of Conduct](CODE_OF_CONDUCT.md)
## 📜 License
Rallly is open-source under the GNU Affero General Public License Version 3 (AGPLv3) or any later version. See [LICENSE](LICENSE) for more detail.
## 💚 Sponsors
Thank you to our sponsors for making this project possible.
[Become a sponsor →](https://github.com/sponsors/lukevella)
---
### Overview (`apps/docs/README.md`)
# Support Docs
Live site: [https://support.rallly.co](https://support.rallly.co)
Our docs are written in [MDX](https://mdxjs.com/) which is mostly [Markdown](https://www.markdownguide.org/cheat-sheet) with the ability to use components inside.
This site is kindly built with and hosted by [Mintlify](https://mintlify.com).
## How to Run Locally
To preview your changes locally, you can use the [mintlify cli](https://mintlify.com/docs/development) to run a development server.
Install the cli globally:
```bash
pnpm install mintlify
```
Navigate to this directory (where you can find `mint.json`):
```bash
cd apps/docs
```
Start the development server:
```bash
mintlify dev
```
## Components
Mintlify provides a number of useful built-in components such as [Accordion](https://mintlify.com/docs/components/accordion), [Tabs](https://mintlify.com/docs/components/tabs) and [Callouts](https://mintlify.com/docs/components/callouts). Check out their [documentation](https://mintlify.com/docs/components) to see the full list of components with examples.
---
### Apps Docs Biome.Json (`apps/docs/biome.json`)
{
"$schema": "https://biomejs.dev/schemas/2.3.14/schema.json",
"extends": "//",
"files": {
"includes": ["**", "!!api-reference/openapi.json"]
}
}
---
### Apps Docs Docs.Json (`apps/docs/docs.json`)
{
"$schema": "https://mintlify.com/docs.json",
"theme": "mint",
"name": "Rallly",
"colors": {
"primary": "#4f46e5",
"light": "#847eed",
"dark": "#4f46e5"
},
"favicon": "/favicon.png",
"navigation": {
"tabs": [
{
"tab": "Documentation",
"groups": [
{
"group": "Get Started",
"pages": ["introduction", "faq"]
},
{
"group": "How it works",
"pages": ["workflow/create", "workflow/invite", "workflow/schedule"]
},
{
"group": "Spaces",
"pages": [
"spaces/introduction",
"spaces/managing-seats",
"spaces/members",
"spaces/collaboration",
"spaces/billing",
"spaces/custom-branding"
]
},
{
"group": "Integrations",
"pages": [
"integrations/google-meet",
"integrations/zoom",
"integrations/microsoft-teams",
"integrations/webex"
]
},
{
"group": "Guides",
"pages": ["guide/participant-guide", "guide/content-moderation"]
},
{
"group": "Contact",
"pages": ["contact/support"]
}
]
},
{
"tab": "Self-Hosting",
"groups": [
{
"group": "Get Started",
"pages": [
"self-hosting/introduction",
"self-hosting/installation/docker",
"self-hosting/configuration",
"self-hosting/single-sign-on",
"self-hosting/conferencing"
]
},
{
"group": "Advanced",
"pages": [
"self-hosting/management",
"self-hosting/licensing",
"self-hosting/corporate-networks",
"self-hosting/white-labeling"
]
},
{
"group": "Guides",
"pages": ["self-hosting/control-panel", "self-hosting/migration"]
},
{
"group": "Misc",
"pages": ["self-hosting/managed-hosting"]
}
]
},
{
"tab": "API Reference",
"groups": [
{
"group": "Getting started",
"pages": [
"api-reference/introduction",
"api-reference/authentication",
"api-reference/rate-limits",
"api-reference/errors",
"api-reference/changelog",
"api-reference/migrating-from-the-private-api"
]
},
{
"group": "Polls",
"openapi": "/api-reference/openapi.json",
"pages": [
"POST /v1/polls",
"GET /v1/polls",
"GET /v1/polls/{pollId}",
"DELETE /v1/polls/{pollId}",
"GET /v1/polls/{pollId}/results",
"GET /v1/polls/{pollId}/participants",
"GET /v1/polls/{pollId}/participants/{participantId}"
]
},
{
"group": "Webhooks",
"pages": [
"api-reference/webhooks",
"api-reference/webhooks/events",
"api-reference/webhooks/security",
{
"group": "Guides",
"pages": ["api-reference/webhooks/guides/n8n"],
"icon": "book-open"
}
],
"tag": "Beta"
}
]
},
{
"tab": "Contribute",
"groups": [
{
"group": "Contribute",
"pages": ["contribute/introduction"]
},
{
"group": "How to Contribute",
"pages": [
"contribute/donations",
"contribute/translations",
"contribute/documentation"
]
}
]
}
]
},
"logo": {
"light": "/logo/light.svg",
"dark": "/logo/dark.svg",
"href": "https://rallly.co"
},
"background": {
"color": {
"light": "#FFFFFF",
"dark": "#18181B"
}
},
"navbar": {
"links": [
{
"label": "Contact",
"href": "https://support.rallly.co/contact/support"
}
],
"primary": {
"type": "button",
"label": "Go to app",
"href": "https://app.rallly.co"
}
},
"footer": {
"socials": {
"twitter": "https://twitter.com/ralllyco",
"linkedin": "https://www.linkedin.com/company/rallly/",
"github": "https://github.com/lukevella/rallly",
"discord": "https://discord.com/invite/uzg4ZcHbuM",
"website": "https://rallly.co/"
}
},
"redirects": [
{
"source": "/administrators/creating-a-meeting-poll",
"destination": "/workflow/create"
},
{
"source": "/administrators/sharing-a-meeting-poll",
"destination": "/workflow/invite"
},
{
"source": "/participants/submitting-a-response",
"destination": "/guide/participant-guide"
},
{
"source": "/participants/editing-a-response",
"destination": "/guide/participant-guide"
},
{
"source": "/self-hosting/pricing",
"destination": "/self-hosting/licensing"
},
{
"source": "/workflow/finalize",
"destination": "/workflow/schedule"
}
]
}
---
### Apps Docs Faq (`apps/docs/faq.mdx`)
---
icon: "message-question"
title: "FAQ"
description: "Frequently asked questions about Rallly."
---
## What is Rallly?
Rallly is a tool for creating scheduling polls. It's designed to help people find a common time to schedule a meeting or event.
> Rallly is pronounced like "rally" but with an extra _L_.
>
> I wanted to call the product "Rally" because that's what it's for - rallying people together to make things happen.
> But, of course, the domain name was already taken. So, I did what any sane person would do - I added an extra _L_.
>
> -- [Luke Vella](https://twitter.com/imlukevella), Creator of Rallly
## What is a Scheduling Poll?
Scheduling polls help you find a time that works for everyone. The host
of the meeting will typically select a few date and time options for participants to vote
for and then select the most suitable option.
1. Click **Delete** to confirm
---
### Apps Docs Administrators Editing A Meeting Poll (`apps/docs/administrators/editing-a-meeting-poll.mdx`)
---
title: "Edit a Poll"
description: "How to make changes to an existing meeting poll."
---
Everything about a poll is edited on one page: its details, its dates and
times, and its settings.
**Event** - Change the title, location or description.
**Calendar** - Add or remove options using the calendar. Switch
between month and week view, change the duration, or make the poll all
day.
**Settings** - Require an email address from participants, hide
participant names, hide votes until a participant has voted, allow
comments, and choose the vote options.
## Submitting a Pull Request
Submitting a pull request is a great way to fix minor issues like typos or broken links.
Click on the "pencil" icon and fork our repository to submit a pull request.
## Creating an Issue
For larger tasks, you can create a new issue by clicking on the "exclamation" icon.
---
### Apps Docs Contribute Donations (`apps/docs/contribute/donations.mdx`)
---
title: Donations
icon: coins
description: Help fund this project and keep it ad-free
---
## Why should I donate?
Most users of Rallly use it for free, and that's great!
However, running Rallly costs money.
By donating, you can help keep Rallly running and ad-free.
## How can I donate?
You can donate using any of the following methods:
## Tips for Translators
Here are a few things to keep in mind when translating.
### Punctuation
Pay close attention to how phrases are punctuated.
```
Name:
```
If a sentence ends with a period (.) or a colon (:), you will want to include that in your translation.
```
❌ Nombre
✅ Nombre:
```
### Variables
Variables are placeholders for content that can change. They look like this:
```
Hi {name}, welcome back!
```
`{name}` is a variable that will be replaced with the user's name. Please make sure variables remain unchanged when translating.
```
❌ Salut {nom}, bienvenue!
✅ Salut {name}, bienvenue!
```
### Tags
Tags can be used to create a hyperlink or change the appearance of some text (ex. bold, italics etc…). They look like this:
```
Go to page
```
The tags should remain wrapped around the same content and should not be translated. The contents between the tags should be translated (unless they are a [variable](#variables)).
```
❌ Gehen Sie zur Seite
❌ Gehen Sie zur Seite
❌ Gehen Sie zur page
✅ Gehen Sie zur Seite
```
### Plurals
### Register
For languages that have different registers (informal vs. formal), the general advise is to use an **informal** register. However, there may be exceptions for certain languages so if you are not sure please [reach out](#contact).
## FAQ
When you're done, click **Continue**.
The form shows "Google Meet" as the video call for this poll.
If your Google Meet account is not connected, the form tells you so and links to Conferencing settings.
Participants see "Google Meet" on the poll page while voting is open. No meeting link exists yet.
### Finalizing the poll
When you finalize the poll and pick the winning time, Rallly:
1. Creates a Google Meet meeting space on your Google account.
2. Attaches the meeting link to the event.
3. Includes the link in the calendar invite (`.ics`) and in the confirmation emails sent to you and to participants.
A meeting space is a reusable Meet room with its own link. It is not a Google Calendar event, so Rallly does not add anything to your Google Calendar through this integration, and the link is not tied to the scheduled time.
If the link cannot be created, for example because the Google connection has expired or was removed, the poll stays open and Rallly shows an error. Reconnect your account in Conferencing settings and finalize again.
### Which account hosts the meeting
The meeting space is created on the Google account of the poll's organizer. If a space member finalizes a poll organized by someone else, the meeting is still created on the organizer's Google account, and the organizer is the host.
## Permissions
When you connect, Rallly asks Google for these permissions:
| Permission | Why |
| --- | --- |
| Create, edit and see information about the Google Meet conferences Rallly creates (`meetings.space.created`) | To create the meeting space when you finalize a poll. |
| See your primary Google Account email address (`userinfo.email`) | To identify the connection and show which account is connected. |
| See your personal info (`userinfo.profile`) | Requested with the email address to identify the account. Rallly does not store your name or profile picture. |
The `meetings.space.created` permission only lets Rallly create meeting spaces and manage the spaces it created itself. Rallly does not read your other meetings, recordings, transcripts, participants, contacts or email, and does not join or record meetings.
## Data Rallly stores
For a connected Google account, Rallly stores:
- Your Google account id and email address, to identify the connection and show it in your settings.
- The access token and refresh token Google issues, encrypted at rest, so Rallly can create meeting spaces on your behalf without asking you to sign in each time. If the same Google account is also connected for Google Calendar, both connections share these tokens.
For each finalized poll, Rallly stores the link and meeting code of the meeting space it created, as part of the event.
Rallly does not store the content of any meeting.
## Removing the app
### From Rallly
1. Open **Settings**, then **Conferencing**.
2. Next to **Google Meet**, click the **More options** button and choose **Disconnect**.
The connection is removed immediately and Rallly stops creating Google Meet links for you. What happens to the tokens depends on whether the same Google account is connected for Google Calendar:
- If it is not, Rallly deletes the tokens it stored for that Google account.
- If it is, Rallly keeps the tokens, because your calendar connection still needs them.
Disconnecting in Rallly does not revoke the access you granted in your Google account, because the same Google access can also serve your calendar connection. To revoke it, remove Rallly from your Google account as described below.
Polls that already chose Google Meet keep that choice but can no longer be finalized with a Google Meet link until an account is connected again. Links Rallly already created keep working.
### From your Google account
To revoke Rallly's access on the Google side:
1. Open the [third party apps and services](https://myaccount.google.com/connections) page of your Google account.
2. Select **Rallly**.
3. Click **Delete all connections you have with Rallly** and confirm.
This revokes every permission Rallly holds on that Google account, including Google Calendar access if you connected it. Google does not tell Rallly, so the connections still appear in your settings until you disconnect them in Rallly as well; Rallly can no longer use them. If you sign in to Rallly with Google, you can still do so; Google asks you to approve Rallly again the next time.
## Troubleshooting
**"Google Meet is not connected" when creating a poll.** Your Rallly account has no Google Meet connection, or it was removed. Connect one in Conferencing settings and choose Google Meet again.
**Finalizing fails with a video call error.** The Google connection has expired, Rallly's access was removed from your Google account, or the Google Meet permission was not selected when you connected. Disconnect and reconnect Google Meet in Conferencing settings, then finalize again. The poll is unchanged until finalizing succeeds.
**Google blocks the connection.** On a Google Workspace account, your administrator may not allow third party apps or may have turned off Google Meet for your account. Ask your administrator to allow Rallly, or connect a different Google account.
**Participants have to ask to join.** Who can join without asking follows the Meet settings of the host's Google account or Workspace organization. The host can admit people from the meeting, or change the meeting access in Meet's host controls.
**The meeting was created on the wrong account.** The meeting is always created on the poll organizer's connected Google account. Check which account is connected in Conferencing settings.
Still stuck? [Contact support](/contact/support).
---
### Apps Docs Integrations Microsoft Teams (`apps/docs/integrations/microsoft-teams.mdx`)
---
icon: video
title: Microsoft Teams
description: Connect your Microsoft work or school account so Rallly creates the Teams meeting link when you finalize a poll
---
With the Microsoft Teams integration, Rallly creates a Teams meeting on your Microsoft account at the moment you finalize a poll. The join link goes into the event, the calendar invite and the confirmation emails, so participants never wait for a link to follow.
If your Microsoft Teams account is not connected, the form tells you so and links to Conferencing settings.
Participants see "Microsoft Teams" on the poll page while voting is open. No meeting link exists yet.
### Finalizing the poll
When you finalize the poll and pick the winning time, Rallly:
1. Creates a Teams meeting for that time on your Microsoft account.
2. Attaches the join link, meeting ID and passcode to the event.
3. Includes them in the calendar invite (`.ics`) and in the confirmation emails sent to you and to participants.
Rallly does not add the meeting to your Outlook calendar; the calendar invite Rallly sends covers it.
If the meeting cannot be created, for example because the Microsoft connection has expired or your account no longer has a Teams license, the poll stays open and Rallly shows an error that says which it is. See [Troubleshooting](#troubleshooting).
### Which account hosts the meeting
The meeting is created on the Microsoft account of the poll's organizer. If a space member finalizes a poll organized by someone else, the meeting is still created on the organizer's Microsoft account, and the organizer is the host.
## Permissions
When you connect, Rallly asks Microsoft for these permissions:
| Permission | Why |
| --- | --- |
| Read and create your online meetings (`OnlineMeetings.ReadWrite`) | To create the Teams meeting when you finalize a poll, and to check once, when you connect, that your account can create meetings. |
| Sign you in and read your profile (`User.Read`) | To identify the connection and show which account is connected. |
| Maintain access to data you have given it access to (`offline_access`) | So Rallly can create meetings when you finalize a poll without asking you to sign in each time. |
| View your basic profile and email address (`openid`, `profile`, `email`) | Requested with the sign in to identify the account. Rallly does not store your name. |
Rallly uses `OnlineMeetings.ReadWrite` only to create a meeting when you finalize a poll and to create and immediately delete one test meeting when you connect. Rallly does not read your other meetings, chats, recordings, transcripts, files, contacts, calendar or email, and does not join or record meetings.
## Data Rallly stores
For a connected Microsoft account, Rallly stores:
- Your Microsoft account id and email address, to identify the connection and show it in your settings.
- The access token and refresh token Microsoft issues, encrypted at rest, so Rallly can create meetings on your behalf without asking you to sign in each time.
For each finalized poll, Rallly stores the join link, meeting ID and passcode of the meeting it created, as part of the event.
Rallly does not store the content of any meeting.
## Removing the app
### From Rallly
1. Open **Settings**, then **Conferencing**.
2. Next to **Microsoft Teams**, click the **More options** button and choose **Disconnect**.
The connection is removed immediately, Rallly deletes the tokens it stored for that Microsoft account and stops creating Teams meetings for you.
Microsoft does not let apps revoke their own access, so disconnecting in Rallly does not remove Rallly from your Microsoft account. Rallly no longer holds tokens to use it, but to remove the permission itself, follow the steps below.
Polls that already chose Microsoft Teams keep that choice but can no longer be finalized with a Teams link until an account is connected again. Meetings Rallly already created keep working.
### From your Microsoft account
1. Open [My Apps](https://myapps.microsoft.com) and sign in with the account you connected.
2. Find **Rallly**, open its menu and choose **Manage your application**.
3. Choose **Revoke permissions** and confirm.
If you do not see the option, your organization manages app permissions centrally; ask your administrator to remove Rallly. Microsoft does not tell Rallly, so the connection still appears in your settings until you disconnect it in Rallly as well; Rallly can no longer use it.
## Troubleshooting
**Microsoft says "Need admin approval".** Your organization does not let users approve apps. Send your administrator the link described under [Admin approval](#admin-approval).
**Microsoft does not accept your personal account.** Microsoft Teams meetings can only be created for work or school accounts. Connect the account your organization gave you.
**Rallly says the account can't create Teams meetings.** Microsoft refused the test meeting Rallly creates when you connect. The account has no Teams license, Teams has never been opened with it, or your organization's policies do not let it create meetings. Open [Teams](https://teams.microsoft.com) with that account: if Teams does not open, ask your IT administrator for a license that includes Teams. Once Teams opens, connect the account in Rallly again.
**"Microsoft Teams is not connected" when creating a poll.** Your Rallly account has no Microsoft Teams connection, or it was removed. Connect one in Conferencing settings and choose Microsoft Teams again.
**Finalizing fails because Microsoft Teams couldn't create the meeting.** The account could create meetings when you connected it and no longer can, usually because its Teams license was removed. Check that you can open Teams with that account, then finalize again. The poll is unchanged until finalizing succeeds.
**Finalizing fails because the account is not connected.** The connection expired after 90 days without use, your password was changed, or your administrator removed Rallly. Disconnect and reconnect Microsoft Teams in Conferencing settings and finalize again.
**Participants wait in the lobby.** Who waits in the lobby follows your organization's Teams meeting policies. The host can admit people from the meeting, or change the meeting options in Teams.
**The meeting was created on the wrong account.** The meeting is always created on the poll organizer's connected Microsoft account. Check which account is connected in Conferencing settings.
Still stuck? [Contact support](/contact/support).
---
### Apps Docs Integrations Webex (`apps/docs/integrations/webex.mdx`)
---
icon: video
title: Webex
description: Connect your Webex account so Rallly creates the Webex meeting link when you finalize a poll
---
With the Webex integration, Rallly creates a Webex meeting on your account at the moment you finalize a poll. The join link goes into the event, the calendar invite and the confirmation emails, so participants never wait for a link to follow.
If your Webex account is not connected, the form tells you so and links to Conferencing settings.
Participants see "Webex" on the poll page while voting is open. No meeting link exists yet.
### Finalizing the poll
When you finalize the poll and pick the winning time, Rallly:
1. Creates a Webex meeting for that time on your Webex account.
2. Attaches the join link, meeting number and password to the event.
3. Includes them in the calendar invite (`.ics`) and in the confirmation emails sent to you and to participants.
Rallly asks Webex not to send its own invitation emails; the invite Rallly sends covers it.
Webex only schedules meetings between 10 minutes and 23 hours 59 minutes long that have not started yet. Rallly fits the Webex meeting to those limits: an all day event gets a meeting of 23 hours 59 minutes, an event shorter than 10 minutes gets a 10 minute meeting, and an event that has already started gets a meeting that starts at the next minute. The event itself keeps the time you picked.
If the meeting cannot be created, for example because the Webex connection has expired, the poll stays open and Rallly shows an error. See [Troubleshooting](#troubleshooting).
### Which account hosts the meeting
The meeting is created on the Webex account of the poll's organizer. If a space member finalizes a poll organized by someone else, the meeting is still created on the organizer's Webex account, and the organizer is the host.
## Permissions
When you connect, Rallly asks Webex for these permissions:
| Permission | Why |
| --- | --- |
| Create, manage, or cancel your scheduled Webex meetings (`meeting:schedules_write`) | To create the meeting when you finalize a poll. |
| Read your users' company directory (`spark:people_read`) | To read your Webex account id, email address and name, which identify the connection and show which account is connected. |
Rallly uses `meeting:schedules_write` only to create a meeting when you finalize a poll, and `spark:people_read` only to read your own profile. Rallly does not read your existing meetings, messages, recordings, transcripts or contacts, and does not join or record meetings.
## Data Rallly stores
For a connected Webex account, Rallly stores:
- Your Webex account id and email address, to identify the connection and show it in your settings.
- The access token and refresh token Webex issues, encrypted at rest, so Rallly can create meetings on your behalf without asking you to sign in each time.
For each finalized poll, Rallly stores the join link, meeting number and password of the meeting it created, as part of the event.
Rallly does not store the content of any meeting.
## Removing the app
1. Open **Settings**, then **Conferencing**.
2. Next to **Webex**, click the **More options** button and choose **Disconnect**.
The connection is removed immediately, Rallly deletes the tokens it stored for that Webex account and stops creating Webex meetings for you. Polls that already chose Webex keep that choice but can no longer be finalized with a Webex link until an account is connected again. Meetings Rallly already created stay in your Webex account; delete them from Webex if you no longer need them.
## Troubleshooting
**Webex refuses the connection.** Your organization blocks Webex integrations. Ask your Webex administrator to allow Rallly; see [Organization restrictions](#organization-restrictions).
**"Webex is not connected" when creating a poll.** Your Rallly account has no Webex connection, or it was removed. Connect one in Conferencing settings and choose Webex again.
**Finalizing fails because the account is not connected.** The connection expired after a long period without use, or your administrator removed Rallly. Disconnect and reconnect Webex in Conferencing settings and finalize again.
**Finalizing fails because the meeting link couldn't be created.** The connected account may not be able to host meetings, for example a Webex account that only has messaging. Check that you can schedule a meeting in Webex with that account, then finalize again. The poll is unchanged until finalizing succeeds.
**The meeting was created on the wrong account.** The meeting is always created on the poll organizer's connected Webex account. Check which account is connected in Conferencing settings.
Still stuck? [Contact support](/contact/support).
---
### Apps Docs Integrations Zoom (`apps/docs/integrations/zoom.mdx`)
---
icon: video
title: Zoom
description: Connect your Zoom account so Rallly creates the meeting link when you finalize a poll
---
With the Zoom integration, Rallly creates a Zoom meeting on your account at the moment you finalize a poll. The join link goes into the event, the calendar invite and the confirmation emails, so participants never wait for a link to follow.
The form shows "Zoom" as the video call for this poll.
If your Zoom account is not connected, the form tells you so and links to Conferencing settings.
Participants see "Zoom" on the poll page while voting is open. No meeting exists yet.
### Finalizing the poll
When you finalize the poll and pick the winning time, Rallly:
1. Creates a scheduled Zoom meeting on your account for that date and time, using the poll title as the meeting topic.
2. Attaches the join link to the event.
3. Includes the link in the calendar invite (`.ics`) and in the confirmation emails sent to you and to participants.
The meeting also appears in your Zoom account under **Meetings**, where you can edit or delete it like any other meeting.
If the meeting cannot be created, for example because the Zoom connection has expired, the poll stays open and Rallly shows an error. Reconnect your account in Conferencing settings and finalize again.
### Which account hosts the meeting
The meeting is created on the Zoom account of the poll's organizer. If a space member finalizes a poll organized by someone else, the meeting is still created on the organizer's Zoom account.
## Permissions
When you connect, Rallly asks Zoom for these permissions:
| Permission | Why |
| --- | --- |
| View your user information (`user:read:user`) | To read your Zoom account id and email, which identify the connection and show which account is connected. |
| Create meetings (`meeting:write:meeting`) | To create the meeting when you finalize a poll. |
Rallly does not read your existing meetings, recordings, contacts or chat, and does not join or record meetings.
## Data Rallly stores
For a connected Zoom account, Rallly stores:
- Your Zoom account id and email address, to identify the connection and show it in your settings.
- The access token and refresh token Zoom issues, encrypted at rest, so Rallly can create meetings on your behalf without asking you to sign in each time.
For each finalized poll, Rallly stores the meeting id, join link and passcode of the meeting it created, as part of the event.
Rallly does not store the content of any meeting.
## Removing the app
### From Rallly
1. Open **Settings**, then **Conferencing**.
2. Next to **Zoom**, click the **More options** button and choose **Disconnect**.
The connection is removed immediately: Rallly deletes the account details and tokens it stored, then asks Zoom to revoke its access. To confirm the access is gone, remove the app from Zoom as described below. Polls that already chose Zoom keep that choice but can no longer be finalized with a Zoom link until an account is connected again. Meetings Rallly already created stay in your Zoom account; delete them from Zoom if you no longer need them.
### From Zoom
You can also remove the app from the Zoom side:
1. Sign in to the [Zoom App Marketplace](https://marketplace.zoom.us/).
2. Click **Manage**, then **Added Apps**.
3. Find **Rallly** and click **Remove**.
Removing the app from Zoom revokes Rallly's access. Zoom tells Rallly, which deletes the connection and the tokens it stored, so the account no longer appears in your settings. If the account still appears in your settings, disconnect it in Rallly as well.
## Troubleshooting
**"Zoom is not connected" when creating a poll.** Your Rallly account has no Zoom connection, or it was removed. Connect one in Conferencing settings and choose Zoom again.
**Finalizing fails with a video call error.** The Zoom connection has expired or was revoked on the Zoom side. Disconnect and reconnect the account, then finalize again. The poll is unchanged until finalizing succeeds.
**The meeting was created on the wrong account.** The meeting is always created on the poll organizer's connected Zoom account. Check which account is connected in Conferencing settings.
Still stuck? [Contact support](/contact/support).
---
### Apps Docs Self Hosting Conferencing (`apps/docs/self-hosting/conferencing.mdx`)
---
icon: video
title: Video Conferencing
description: Let organizers add Google Meet, Zoom, Microsoft Teams and Webex links to their polls.
---
The Control Panel is your central hub for administering your self-hosted Rallly instance. From here, you can manage users, activate your license, and configure instance-specific settings.
To access the Control Panel:
1. Ensure your Rallly instance is running.
2. Open your web browser and navigate to `/control-panel`.
3. You may be prompted to log in if you haven't already. Only users with administrative privileges can access the Control Panel features.
## Claiming Initial Admin Rights
The first user designated as an administrator needs to manually claim their admin role. This user is specified by the `INITIAL_ADMIN_EMAIL` environment variable during setup (see [Configuration](/self-hosting/configuration)).
To claim admin rights:
1. Ensure the user account associated with the `INITIAL_ADMIN_EMAIL` has been created (e.g., by logging in once).
2. Navigate to the Control Panel: `/control-panel`.
3. If you are the user specified in `INITIAL_ADMIN_EMAIL` and have not yet claimed admin rights, you should see a section or button prompting you to "Make me an admin".
4. Click this button to elevate your account to an administrator.
Once claimed, this user can manage other users and settings.
## Troubleshooting
If you see an **Administrator access required** message when visiting `/control-panel`, the account you are signed in with does not have the admin role. This usually means:
- The `INITIAL_ADMIN_EMAIL` environment variable is not set, or
- It does not match the email address of the account you are signed in with.
Update `INITIAL_ADMIN_EMAIL` to match your account's email address, restart your instance, and visit `/control-panel` again to claim admin rights. Alternatively, an existing administrator can grant your account the admin role from the **Users** section of the Control Panel.
## Update notifications
The Control Panel home page shows the version your instance is running and whether a newer release is available. The check runs against `api.rallly.co` once an hour and only sends the running version and an anonymous instance identifier. On a restricted network, see [Corporate networks](/self-hosting/corporate-networks#hosts-to-allow).
When a release you have not installed yet contains security fixes, every Control Panel page shows a banner linking to the release notes. If your major version has reached end of life and the fix only shipped in a newer major, the banner links to the migration guide instead. Older instances than 4.16 render the plain update notice and cannot tell you about security fixes, so keep an eye on the [releases page](https://github.com/lukevella/rallly/releases) until you have updated past that version.
---
### Apps Docs Self Hosting Corporate Networks (`apps/docs/self-hosting/corporate-networks.mdx`)
---
icon: network-wired
title: Corporate Networks
description: Run Rallly behind a corporate proxy or TLS-intercepting firewall.
---
Corporate networks often restrict outbound traffic in two ways: all egress must pass through an explicit proxy, and/or outbound TLS is intercepted and re-signed with an internal root certificate authority that Node.js does not trust. Either one breaks Rallly's outbound HTTPS requests. [License activation](/self-hosting/licensing), which connects to `licensing.rallly.co` on port 443, is usually where you notice it first, but any outbound call is affected. Some networks require both fixes below together.
If your server can reach the internet directly and your network does not intercept TLS, none of this applies and you can skip this page.
## Hosts to allow
Rallly makes outbound requests to these hosts, all over HTTPS on port 443. If your firewall filters by destination, allow them.
| Host | Purpose | When blocked |
|:-----|:--------|:-------------|
| `licensing.rallly.co` | License activation and refresh | Activation fails with an error in the Control Panel |
| `api.rallly.co` | Hourly update check: sends the running version and an anonymous instance identifier, receives the latest release and any security advisories affecting your version | Fails silently. The version tile shows no status and you are not told about security updates, so watch the [releases page](https://github.com/lukevella/rallly/releases) instead |
Pulling images with `./rallly.sh update` reaches Docker Hub (`registry-1.docker.io` and `auth.docker.io`), which is governed by Docker's own proxy settings rather than the variables below.
Anything you configure yourself, such as your SMTP server, an identity provider, or external object storage, needs to be reachable too.
## Routing traffic through a proxy
Rallly honours the standard `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables for outbound requests. Set them in `.env`:
```sh
HTTPS_PROXY=http://proxy.internal.example.com:8080
HTTP_PROXY=http://proxy.internal.example.com:8080
NO_PROXY=garage,db
```
### [Elestio](https://elest.io/)
Elestio shares 30% of it's revenue with this project.
[](https://elest.io/open-source/rallly)
---
If you have a provider you'd like to recommend, please [open an issue](https://github.com/lukevella/rallly/issues/new) on Github.
---
### Apps Docs Self Hosting Management (`apps/docs/self-hosting/management.mdx`)
---
icon: terminal
title: Management
description: Operate a self-hosted Rallly instance with the Rallly CLI.
---
The **Rallly CLI** (`rallly.sh`) is the single entry point for day-to-day operations on a self-hosted instance. It ships with the [self-hosted stack](https://github.com/lukevella/rallly-selfhosted) and should be run from the stack directory (e.g. `/opt/rallly` for installer-based setups).
## Commands
```sh
./rallly.sh start # Start all services
./rallly.sh stop # Stop all services
./rallly.sh restart # Restart all services
./rallly.sh status # Show service status
./rallly.sh logs # Stream logs for all services
./rallly.sh logs web # Stream logs for a specific service
./rallly.sh update # Pull latest images and recreate containers
./rallly.sh backup # Back up the database to ./backups/
```
## Applying configuration changes
After editing `.env`, apply changes with:
```sh
./rallly.sh restart
```
## Updating
```sh
./rallly.sh update
```
This pulls the latest Docker images and recreates containers. Your data and configuration are preserved.
By default the stack tracks the `lukevella/rallly:4` tag, so `update` will bring you the latest compatible `4.x` release. To pin to a specific version or follow a different major, set `RALLLY_IMAGE` in `.env` (see [Configuration](/self-hosting/configuration#advanced)).
White labeling allows you to customize the appearance of your Rallly instance to match your organization's branding. You can change the application name, primary colors, logos, and hide attribution text.
## What you can customize
- **App name** - The name displayed in page titles, navigation, and emails
- **Primary colors** - Brand colors for both light and dark modes
- **Logos** - Your own logo for light mode, dark mode, and the icon used in emails
- **Attribution** - Hide the "Powered by Rallly" text in polls and emails
## Configuring branding
Branding is configured from the [Control Panel](/self-hosting/control-panel) under **Branding**. Changes take effect immediately, with no restart required.
1. Sign in as an administrator and go to `/control-panel/branding`.
2. Set the app name, primary colors, logos, and attribution settings.
3. Each field saves on its own, so you can change one setting at a time.
The same settings can also be supplied as environment variables. A value saved in the Control Panel takes precedence over the matching environment variable, and clearing it falls back to the environment variable, then to the Rallly default. Precedence is applied per field, so you can set some values in `.env` and others in the UI.
When a field is backed by an environment variable and has no saved value yet, the Branding page shows a note saying so. Saving a value in the UI overrides it.
## Logos
The three logo slots serve different purposes:
- **Logo** - The wordmark shown on light backgrounds
- **Logo (dark mode)** - The wordmark shown on dark backgrounds. Falls back to the light logo if not set
- **Logo icon** - A square icon shown on polls and at the top of emails
### Uploading a logo
Logo uploads require object storage to be configured. The stack installed by the [Rallly CLI](/self-hosting/installation/docker) includes storage by default, so this works out of the box. If your instance has no storage configured, the Branding page says so and you can point at externally hosted images with `LOGO_URL`, `LOGO_URL_DARK` and `LOGO_ICON_URL` instead. See [External object storage](/self-hosting/configuration#external-object-storage) for the storage variables.
| Slot | Accepted formats | Maximum size |
| --- | --- | --- |
| Logo | SVG, PNG, JPEG | 2 MB |
| Logo (dark mode) | SVG, PNG, JPEG | 2 MB |
| Logo icon | PNG, JPEG | 2 MB |
The logo icon is raster only because it is embedded in emails, where SVG rendering is unreliable across mail clients.
Removing an uploaded logo clears the saved value, so the instance falls back to the environment variable if one is set, and to the Rallly logo otherwise.
### Preparing your logo
There is no logo size setting. On the sign-in and registration pages your wordmark is drawn inside a fixed slot of 192 by 128 pixels, scaled down to fit inside it while keeping its aspect ratio, so it is never cropped or stretched. Elsewhere in the app it is scaled to a fixed height.
Because the slot is fixed, the shape of your asset determines how large it renders:
- Crop the asset tightly to the artwork. Whitespace baked into the file is scaled along with the logo, so a padded asset renders visually smaller than a tight one.
- Prefer SVG for the wordmark logos so they stay sharp at any size. If you upload a raster wordmark, supply it at roughly twice the slot size so it holds up on high density displays.
- Wide, horizontal wordmarks fill the slot better than tall or square ones.
- For the dark mode logo, supply a variant that reads well on a dark background rather than reusing the light one.
The Branding page previews each logo inside the slot it renders in, on the background it will appear against, so you can check the result before rolling it out.
## How branding applies to spaces
There is nothing to configure. The behavior is tied to the white label add-on on your license. Any space branding that was set before is preserved but not shown, so if the add-on is removed, spaces return to using their own branding.
## Environment variables
Use these when you prefer to configure branding from `.env`, or when your instance has no object storage for uploads. Add the values to the `.env` file at the root of your self-hosted stack, then apply them with `./rallly.sh restart`.
```sh
# White labeling
APP_NAME="Acme Scheduler"
PRIMARY_COLOR="#0066cc"
PRIMARY_COLOR_DARK="#3399ff"
LOGO_URL="https://example.com/logo.svg"
LOGO_URL_DARK="https://example.com/logo-dark.svg"
LOGO_ICON_URL="https://example.com/icon.png"
HIDE_ATTRIBUTION="true"
```
The three logo variables must be absolute URLs to images your instance can reach. See the [Configuration Options](/self-hosting/configuration#branding) page for the full list of available settings.
## Requirements
- **Enterprise License with White Label Add-on**: White labeling features are only available with an active Enterprise license that includes the white label add-on.
- Without the add-on, the Branding page is read-only and your instance uses the default Rallly branding regardless of any saved or environment variable settings.
To inquire about Enterprise licensing, please fill out our [Enterprise Requirements Survey](https://app.formbricks.com/s/cmebvnf2ohvjkt901eefxsonr).
---
### Apps Docs Spaces Billing (`apps/docs/spaces/billing.mdx`)
---
icon: "credit-card"
title: "Billing & Seats"
description: "Understanding seat-based pricing, centralized billing, and subscription management for spaces."
---
## How Seat-Based Billing Works
Rallly spaces use a seat-based pricing model that scales with your team size:
#### Adding Seats
When you need to invite more members:
1. **Navigate to Billing Settings**
2. **Click "Manage Seats"**
3. **Increase the seat count** to accommodate new members
4. **Confirm the changes** - billing will be prorated immediately
#### Removing Seats
To reduce costs when team members leave:
1. **Remove members** from your space first
2. **Go to Billing Settings** and click "Manage Seats"
3. **Decrease the seat count** to match your current needs
4. **Confirm the changes** - adjustments will be credited to your next bill
## Turning collaboration on or off
## Requirements
- A Pro space subscription
- Space Owner or Admin role
## Enabling Custom Branding
1. Go to **Settings → General** in your space.
2. Under the **Branding** section, toggle on **Enable Custom Branding**.
3. Use the color picker to choose your primary color.
4. Click **Save** to apply the color.
Once enabled, your primary color will be used on all public-facing poll pages and emails sent to participants.
As responses come in, you can review the results on your poll page to see
which dates are preferred. If you invited people by email, the Share
dialog also shows who has opened their invite and who has responded.
The final date is displayed on your poll for everyone to see and can be
added to a calendar with one click.
