Alby Documentation

Account navigation

• Projects: project cards and shared lifecycle controls.
• Microsites, Vote and Interact: product-specific lists beneath Projects.
• Account Settings: account details plus Members and Billing.
• Your login: in the user pill, manage Change password and Change login email for your personal Alby login.

Project lifecycle and automatic housekeeping

Changing the parent status applies the same status transactionally to attached Microsite, Interact and Vote products. Alby also performs scheduled lifecycle housekeeping.

• Active events normally close after the event end time plus their expiry window.
• Closed events archive 42 days after the event date and time.
• Archived events soft-delete 365 days after the event date and time.
• Soft-deleted events permanently delete 30 days after deletion unless recovered.
• Vote can use its configured event expiry period; other products use the standard post-event window.

Editors, Viewers and project assignments

Assignments are made once on the project. Alby keeps the attached product permissions synchronised.

Combine existing projects

The combine tool can merge compatible projects without changing the underlying product IDs or public URLs.

• Projects cannot be combined when they contain overlapping product types.
• Assignments from the source project are merged.
• Where applicable, Interact and Vote are reconnected to the retained Microsite.
• Always review the combined project before making it Active.

Deleted projects and recovery

Deleting a project is initially a soft deletion. Open the Deleted area to see time remaining, recover the project or permanently delete it.

• Recovery is available during the 30-day window.
• A recovered project returns to Draft.
• Recovery can be blocked when the account no longer has enough product allocation.
• Permanent deletion removes the project and its product data according to Alby’s retention rules.

Delete an account

Account Owners can schedule an Alby account for deletion from Account Settings → Delete Account. Account deletion is deliberately delayed so paid access is preserved and the request can be withdrawn before it takes effect.

1. Review the effective date and the account-deletion consequences shown by Alby.
2. Enter the current password, type the account name exactly and acknowledge the deletion warning.
3. Select Schedule account deletion. All Account Owners are notified of the request.
4. Continue using the account normally until the effective date. Public links, events and member access remain available until then.

How the effective date is chosen

• If the account has an active Stripe subscription, Alby schedules Stripe to cancel at the end of the current paid period and uses that period-end date as the account-deletion date.
• If there is no active subscription period to preserve, Alby uses a 7-day cooling-off period.
• While deletion is scheduled, online plan purchases and billing changes are paused. Withdraw the deletion request first if billing needs to be changed.

Withdraw a scheduled deletion

Before the effective date, an Owner can return to Account Settings → Delete Account and withdraw the request. Alby requires the current password and typed account name again.

• If Alby scheduled a still-resumable Stripe cancellation as part of the deletion request, withdrawing the request restores automatic renewal.
• If the subscription was already scheduled to cancel before the deletion request, or had already ended, withdrawing the Alby deletion request does not create or reactivate a subscription.
• Once the effective date has been reached, the request can no longer be withdrawn online.

What happens when deletion takes effect

• Account memberships are disabled and Microsite, Interact and Vote events enter Deleted state.
• Public links become unavailable, active Vote sessions are invalidated and pending plan changes are cancelled.
• The account enters Alby’s 30-day recoverable deletion state. Recovery during this period is handled by an Alby Super Admin.
• After the recovery window, account data is permanently removed according to Alby’s retention rules.
• Invoices, payments, refunds, Stripe references and audit history may be retained where required for financial, legal and operational records.

Members, invitations and seat limits

Owners and Admins can manage the account team from Account Settings → Members. The available number of seats depends on the account plan.

• The account owner and every active member count toward the member limit.
• An unexpired pending invitation reserves a seat until it is accepted, revoked or expires.
• Inactive users and expired or revoked invitations do not count.
• An existing active Alby user can be added immediately when a seat is available.
• A new user receives a secure invitation email and creates their own password.
• New invited users and existing users joining another account must explicitly agree to the Alby Terms of Service and Privacy Policy before the invitation is accepted.
• Pending invitations can be reviewed, resent, edited or revoked.
• Accepting an invitation that already reserved a seat remains allowed.
• When the member limit is reached, new members, reactivations and renewed invitations are blocked until a seat is freed or the plan is upgraded.

Project access for Editors and Viewers

Open Manage access beside an Editor or Viewer to choose how their project access is granted.

• All projects: grants every current and future project in the account.
• Selected folders: grants every current project in those folders and automatically includes future projects placed there.
• Individual projects: adds specific projects, including projects in Unfiled or exceptions outside the selected folders.
• Moving a project into a selected folder grants inherited access. Moving it out removes inherited access unless the project is also selected individually.
• Deleting a folder moves its projects to Unfiled and removes the inherited folder grants. Individual project grants remain.
• One project grant synchronises the same role to attached Microsite, Interact and Vote products.
• Access can be prepared for a pending invitation, but product access becomes active only after the invitation is accepted.
• Owners and Admins remain account-wide and do not need folder or project assignments.

Your login: Change password, Change login email and Forgot Password

Personal login security lives under Your login in the user pill. These controls affect your own Alby login across every account you belong to. They do not change an account’s billing email.

• Change password: requires the current password and creates a new password that meets Alby’s password policy.
• Change login email: requires the current password, checks that the new address is unused, sends a single-use verification link to the new address, and signs older sessions out after the change is confirmed.
• Forgot Password: sends a single-use reset link to the login email address. The link expires after 60 minutes.
• Passwords require at least 10 characters, including an uppercase letter, a number and a special character.
• A successful reset or confirmed login-email change invalidates older sessions for that login.

Billing, plans and account limits

The Billing area shows the account plan, invoices, receipts and current entitlement usage. Stripe customers can use the customer portal for payment methods and subscription management. Billing management, purchases and plan changes are available only to the account Owner. Admins can view Plan & Usage but cannot access Billing or submit changes.

Free-trial behaviour

• The trial uses the Advanced plan’s event, member, page and template entitlements.
• Signup requires email verification and explicit agreement to the Alby Terms of Service and Privacy Policy.
• Admin pages and authenticated previews remain available during the trial.
• Public Microsite pages, registration and invite links, Interact participant links, Vote voter/observer and public display links, and attendee Zoom joins remain locked.
• Choose any available paid plan from Plan & Usage. Successful payment removes the public-access lock without rebuilding the account or its events.
• A trial can be used once per account. Expiry does not delete the work already created.
• After the trial ends, the account must activate a paid plan to continue normal administration and make public links available.

• Product allocations control how many Microsite, Interact and Vote events the account can retain.
• Deleting an event can free allocation; recovering an event requires available allocation.
• Microsite page limits apply separately to each Microsite and count only normal content pages. Builder system pages do not count.
• Reusable-template limits count only account-wide templates. Built-in Alby templates and event-only templates do not count.
• The owner, active members and unexpired pending invitations count toward the member limit.
• A downgrade takes effect at renewal. If the new plan has lower event allocations, Alby removes the oldest excess events through its safeguarded soft-deletion process.
• Existing members, pages and templates are not automatically removed when a downgrade leaves the account over its new entitlement. The account can edit or remove existing items, but new additions are blocked until usage is reduced or the plan is upgraded.
• After a failed renewal, Alby provides a 14-day grace period. Public links continue during grace and are paused if the grace period expires unresolved.
• Invoices and receipts remain available in the Billing tab.

What Microsites are for

Use a Microsite as the main attendee link for a landing page, livestream, registration journey, virtual event hub, sponsor area, private client event or multi-page conference website.

Microsite access types

Listed, unlisted and search engine indexing

• Listed: the event can appear in Alby public event discovery areas when otherwise eligible.
• Unlisted: the event does not appear in public Alby listings but can still work by direct link.
• Allow search engine indexing: tells external search engines whether they may index public Microsite pages.
• Invite-only and unlisted events are not intended for public discovery.

Page Builder overview

Page Builder stores element positions as percentages so the builder, preview and public page stay aligned.

• Switch between desktop, tablet and phone layouts.
• Drag, resize and configure elements on the artboard.
• Use arrow keys to nudge an element; Shift + arrow moves it faster.
• Use Ctrl/Cmd+C and Ctrl/Cmd+V to copy and paste elements, including between pages.
• Preview before publishing. Saving a layout does not publish the page.

Page Builder elements

Pages, plan limits, home page and publishing

• New Microsite events start with a draft Home page.
• The plan page limit applies to normal content pages in each Microsite: Starter 1, Standard 5, Advanced 25 and Production 50.
• Registration, password, thank-you and other Builder system pages do not count toward the limit.
• Create, duplicate and template-import actions are blocked when they would take the Microsite over its limit.
• Replacing an existing page with one template page does not consume an additional page slot.
• Existing over-limit pages remain editable after a downgrade, but no more pages can be added until usage is reduced or the plan is upgraded.
• Create, duplicate and delete normal pages, and choose which normal page is the Home page.
• Normal pages must be published individually before attendees can view them.
• Navigation using “All Microsite pages” includes published normal pages and excludes system pages.
• System pages appear only when the chosen access type requires them. Their required form block cannot be hidden, deleted or duplicated.

Desktop, tablet and phone layouts

Desktop is the primary design. Tablet and phone layouts can override element position, size and visibility. Phone layouts can automatically stack content as a starting point, then be adjusted manually.

• Preview every device before publishing.
• Use device-specific page backgrounds when the artwork needs different crops.
• Check embeds, Interact, Vote and Zoom at the final public width rather than relying only on the editor placeholder.

Event Theme

Event Theme provides reusable styles across the Microsite while still allowing individual elements to keep local overrides.

• Named rich-text styles for titles, subtitles, headings, body and custom styles.
• Desktop, tablet and phone page backgrounds.
• Primary, Secondary and Plain button presets.
• System form styling for cards, labels, inputs, buttons and messages.
• Defaults for blocks, embeds, colour blocks and navigation.
• Use the per-property Use Event Theme controls to choose exactly which properties inherit the theme.

Templates and template limits

Templates can store normal pages, responsive layouts, matching system-page designs and uploaded Page Builder assets.

• Account templates: reusable across the account and counted against the plan quota: Starter 0, Standard 25, Advanced 100 and Production 500.
• Event templates: available only within the current event and do not count toward the account-template quota.
• Alby Templates: reusable platform templates provided by Alby and available without consuming account-template quota.
• Starter accounts can use Alby templates and save Event templates, but cannot create reusable Account templates.
• When the account-template quota is reached, saving or duplicating another template into Account scope is blocked. Deleting an Account template frees a slot.
• Existing over-limit Account templates are preserved after a downgrade, but no new Account templates can be added until usage is reduced or the plan is upgraded.
• Search, filter by category and inspect the scaled page preview before loading.
• Load all pages or one selected page, and choose whether to replace the current page or add pages. The destination Microsite page limit still applies.
• A template can use the destination Event Theme or carry a fixed copy of the source theme.
• Zoom and Interact connections are removed from saved templates automatically so another event does not inherit live credentials or links.

Registration and attendee management

Choose Registration as the Microsite access type when attendees must register before receiving an individual access link. The Registration system page is created automatically and can be themed in Page Builder.

Registration fields

• First name, last name and email are fixed compulsory registration fields.
• Add up to six optional custom fields after the standard fields.
• Custom fields can accept general text, letters-only text, numbers, a single choice or multiple choices.
• Choice options are entered one per line, and each custom field can be optional or required.
• The Registration system page in Page Builder previews the configured registration fields, including field types and required state.
• The Registration Success system page previews the attendee-facing completion or awaiting-approval state and follows the account preference for whether the Open event button and raw access link are shown.
• Use Manage Registrations in either system page’s Properties panel to jump directly to the registration records.

Registrations and approval

• The Registered tab lists attendee details, custom-field answers, status and source. Registration and Invite-only records can also show their personal access link; Lead Capture does not use attendee access links.
• If registration approval is enabled, a self-service registration remains Awaiting approval until an organiser approves it. Approval generates the attendee access link and sends the confirmation email.
• Confirmed attendees can have their access email resent. Regenerating an access link invalidates the old link.
• Participants can be removed from the event, and linked Alby Vote events can use the Can vote control for confirmed attendees.
• Registration records can be uploaded and exported as CSV. Use Alby’s example CSV headers and save import files as UTF-8.
• Lead Capture de-duplicates by email address: submitting the same email again updates that lead’s stored details rather than creating a duplicate row.

Calendar links

• When the event has a start time, the registration success page includes an Add to my calendar download.
• Registration confirmation emails also include the attendee’s calendar link when available.
• Use {calendar_link} in the confirmation email body to position that link manually.

Confirmation, reminder and feedback emails

For supported Microsite access types, open the event and select Emails. The available tabs depend on the access type. The Logs tab records event-email delivery activity.

Confirmation email

The Confirmation tab is available for Registration events. It is the email that provides the attendee with their personal event access after registration is confirmed.

• For registrations that do not require approval, the confirmation email is sent after successful registration.
• When approval is required, the attendee is told their registration is awaiting approval; the access link and confirmation email are sent when an organiser selects Approve & email link.
• Configure the email subject and body using attendee/event variables.
• Available variables include {first_name}, {last_name}, {event_name}, {event_time}, {access_link} and {calendar_link}.

Reminder emails

Reminder emails are available for Registration and Invite-only events.

• Configure up to six reminders for an event.
• Each reminder has its own enabled switch, internal name, send date/time, subject and body.
• Send date/time is entered in the event timezone; Alby handles the UTC conversion for scheduled delivery.
• Reminders are sent to confirmed attendee records and are logged so the same scheduled reminder is not sent twice to the same attendee.
• Available variables are {first_name}, {last_name}, {event_name}, {event_time} and {access_link}.

Feedback email and Feedback Page

Feedback is available for Registration, Invite-only and Lead Capture events. The Feedback area contains Email, Feedback Page and Feedback Results tabs.

• Email: enable the feedback email, set its subject/body and choose the scheduled send date/time. New or blank templates are pre-populated with default copy containing {feedback_link}, so the unique feedback-page link is included unless the organiser deliberately changes the copy. Email variables also include {first_name}, {last_name}, {event_name}, {event_time} and {access_link}.
• Feedback Page: configure the page heading, introductory text, questions, submit-button label and success message. Questions can be short text, long text, 1–5/1–10 rating, single choice, multiple choice or dropdown, and can be reordered or marked required.
• The Feedback Page heading, introductory text and success message support {first_name}, {last_name}, {event_name} and {event_time}.
• Page Builder: when Feedback email is enabled, the protected Feedback system page appears in Page Builder and previews the configured attendee-facing form. Use Manage Feedback in Properties to return to its setup. Disabling Feedback email hides the system page without deleting its design.
• Feedback availability: disabling Feedback email immediately disables previously issued Feedback links as well as new submissions. Re-enabling it makes the configured Feedback page available again.
• Feedback Results: review submitted responses and rating summaries, then export the feedback results as CSV when required.

Create and configure Interact

1. Create or attach an Interact product to the project.
2. Enable the required tabs: Chat, Q&A, Polls and optional Vote.
3. Open the administration view to prepare pinned messages, Q&A workflow and poll content.
4. Use the standalone public link or add an Interact element to a Microsite page.
5. When an existing Interact event is selected in Page Builder and the page is saved, Alby links that Interact event back to the Microsite and sets audience posting identity to Use linked microsite identity. An Interact event already linked to another Microsite cannot be silently moved from Page Builder.
6. Set the project to Active when attendee access should begin.

Chat

• Attendees and administrators can post into the live chat feed.
• Administrators can pin and unpin a message from the message menu.
• The pinned message remains at the top while the live feed continues below.
• Direct participant messaging can be enabled or disabled for the event.
• Chat records can be exported as CSV.

Q&A

• Collect attendee questions in the Q&A tab.
• Administrators can explicitly select one question for the presenter or on-air display.
• If no question is selected for display, the selected-question output remains blank. It does not automatically fall back to the highest-ranked question.
• The presenter view provides a clean question list for speakers or moderators.
• The on-air/lower-thirds output can use a transparent background for production overlays.
• Q&A records can be exported as CSV.

Polls and poll groups

Available poll types include ordinary choice, multiple choice, word cloud, quiz, rating and open text.

• Quiz polls allow one submitted attempt per participant per round. After submission, that participant cannot change the response during the same round.
• Quiz feedback has two independent controls: Show if answer is correct/incorrect, and Show correct answer after submission. Both are off by default; revealing the correct answer also enables correct/incorrect feedback.
• Closing a Quiz preserves that round. Reopening it starts a fresh round, clears the active results and gives every participant one new attempt, while previous rounds remain available in history and exports.
• Poll groups run an ordered sequence with a Next control and progress such as 3/8. Reopening a group also starts fresh rounds for closed Quiz polls in that group.
• When a poll opens, the tabbed Audience view — including an Interact element embedded in a Microsite — automatically switches to the Polls tab. Q&A and Chat tabs can show unread activity badges while the attendee is viewing another tab.
• Non-quiz polls retain their normal response-update behaviour when the poll is open.
• Poll results can be exported as CSV and as a formatted PDF with charts; Quiz history includes its round numbers.

Exports

Q&A, Chat and Poll CSV exports are available to authorised users for the event. Poll results can also be exported as PDF.

Presenter and On-Air views

• The Presenter view is designed for speakers, moderators and stage teams.
• The On-Air view provides clean Q&A and Poll outputs with vertical tabs.
• Transparent backgrounds are available for keying or browser overlays.
• Display controls in Interact settings govern the available production outputs.

Production links and data feeds

The Display tab and Settings → Links show complete absolute URLs for public, presenter, on-air and data-feed outputs. The visible URL, Copy action and Open action use the same address.

• Regenerate public links: authorised event managers can regenerate the Interact public token from Settings → Links. Existing Audience, Q&A, Chat, Polls, Presenter, On-Air, JSON and XML URLs stop working immediately.
• Linked Microsites: the Microsite relationship is stored against the Interact event, so an embedded Interact element automatically resolves the current public token after regeneration and does not need to be resaved.

Display JSON

The public JSON feed is intended for live presentation/display use. It contains the current event display state, eligible Q&A state and the currently open poll/results required by display consumers.

Display XML / vMix

The Display XML feed combines the current display state, selected and top Q&A questions, and results for the poll that is currently open. Copy the event-specific Display XML URL from Alby Interact.

Display XML XPath reference

Q&A-only XML behaviour

The Q&A-only XML feed is designed for vMix Data Sources when the complete live ranked question list is required. Copy the event-specific Q&A-only XML URL from Alby Interact.

• Selected for display: contains only the question explicitly selected in Alby Interact. When nothing is selected, these fields are blank.
• Top question: contains the question currently ranked first by the live Q&A ordering.
• Question positions: contains every eligible question as a repeated row in current rank order. Upvotes and downvotes can therefore move a question between vMix rows.
• Selecting a question for display changes only the selected block; it does not remove or reorder the full ranked list.
• Hidden, rejected and deleted questions are excluded from the public XML list.

Q&A-only XML XPath reference

Companion fields are available beneath the same selected, top or repeated question node: question_id, author_name, organisation, upvotes, downvotes, net_score, status and submitted_at.

Vote tab and Microsite integration

An attached Vote event can appear as a tab inside Interact. When Interact is embedded in a Microsite that captures attendee identity, Alby can pass that attendee identity into Q&A, Chat, Polls and the supported Vote experience.

• The same attendee identity is retained while moving between supported Interact tabs.
• Microsite identity is scoped to the linked event and is not transferred to another account or another Interact event.
• A new standalone/private browser session uses that Interact event's normal standalone identity behaviour rather than inheriting a previous Microsite attendee identity.

Interact troubleshooting

• Nothing appears publicly: confirm the project and Interact product are Active.
• Embed is missing: confirm the Microsite page is published and the Interact element points to the correct event. Saving a manually selected Interact event in Page Builder should also show that Microsite under Interact settings.
• Question is not on air: select it in the administration view and check the display mode.
• Poll does not switch into view: confirm the Interact event is Active and the Audience/embedded Interact page is using the current public link.
• Vote tab is missing: confirm Vote is attached, enabled and Active.
• Attendee name is missing: confirm the Microsite captures identity, is shown as the linked Microsite in Interact settings, and Audience posting identity is set to Use linked microsite identity.

Create a Vote event

1. Create or attach Vote to the project.
2. Set the event date, access and voting defaults.
3. Add voters and any observers manually or by CSV.
4. Create questions and confirm the voting mode, abstain setting and change-vote rule.
5. Test voter, Facilitator, Who Voted and On-Air links before the event.
6. Set the project to Active before voters need public access.

Voters, observers and CSV import

• Voters are eligible to cast votes according to their configured weight and permissions.
• Observers can monitor the voter experience without being counted as eligible voters.
• A voter email address identifies one voter record within a Vote event. Duplicate voter emails are blocked.
• When the same attendee reaches Vote through a linked Microsite and through a standalone voter link, Alby resolves those access paths to the same voter identity where they can be safely matched.
• CSV import supports duplicate handling and provides an audit record.
• Use the downloadable example CSV and UTF-8 encoding to avoid header or character problems.

Voter access and sessions

• Each voter can receive a unique access link.
• Events can optionally require an additional voter ID and PIN.
• Only one active session is allowed per voter. Opening the same voter access in another independent browser/device ends the earlier Vote session.
• Regenerating a voter link invalidates the old link and ends sessions created by it without affecting other voters.
• Linked Microsite access and standalone voter-link access can both resolve to the same voter record; they are access methods, not separate voter identities.
• The holding page is shown when voting is not currently open.

Voting modes

• Ordinary: each eligible voter has the standard vote value.
• Weighted: a voter’s configured weight is applied to the selected option.
• Split weighted: an eligible voter can distribute their weight according to the question rules.
• Abstain: enabled by default or overridden per question.
• Allow change: lets voters revise their selection while the question remains open.

Questions, opening and rounds

The event administration controls which question is current and whether it is open. Closing a question stops new votes. Reopening creates a new round so the previous results and audit history remain intact.

• Confirm the current question before opening voting.
• Opening another question finalises any previously open round first, including a round in which no votes were cast.
• Use the Who Voted view to monitor participation without exposing vote choices.
• Public result and participation data becomes available only after the question closes.
• Every opened round is retained in Results and Round History exports, including zero-vote rounds.

Results, On-Air and exports

• The On-Air view provides a clean results display using horizontal bars or pass/fail output, as appropriate.
• The public JSON and vMix XML feeds expose the current open question or the most recently closed question. While voting is open they withhold vote totals, option percentages, participation and weighted-cast values. Those values become available after the question closes.
• Public display feeds do not include Vote theme configuration, internal round IDs/numbers, Who Voted data, voter access links, PINs or session identifiers.
• Exports include Voters CSV, Results CSV, Round History CSV, Audit CSV and Organisation CSV. Results and Round History retain every opened round, including rounds closed with no votes cast.
• Vote CSV exports neutralise spreadsheet-formula prefixes (=, +, - and @) and normal reporting exports do not include voter access URLs or session IDs.
• The Audit CSV records operational actions such as voter access claims, votes submitted/changed, voter/question edits, and question open/close actions, including useful actor and change details without exposing access credentials.
• The Facilitator and Who Voted pages are authenticated, display-only tools. They are available only while the Vote event is Active.
• Viewer access is read-only: management and voter-link controls are disabled, while permitted reporting/display access remains available.

Alby Vote XML / vMix

Open the Vote event, go to Settings → Links and copy the vMix XML Feed URL. The same link is also available from the On Air settings. Use that event-specific URL as the XML data source in vMix.

Alby Vote XML XPath reference

Microsite and Interact embedding

Vote can be available through its standalone voter link, an Alby Vote element on a Microsite or a Vote tab inside Interact. Registered Microsite identity can be handed into the Vote experience where configured.

• Microsite identity is scoped to the linked Vote event and does not carry a voter identity into another Vote event.
• When a matching voter already exists, Microsite access reuses that voter record rather than creating a second eligible voter.
• Standalone voter links continue to work for the same voter record and retain the one-active-session rule.

Vote troubleshooting

• No question appears: confirm a current question has been opened.
• Voter cannot enter: confirm Vote is Active, the link is current and the voter is enabled.
• Session ended: the same voter access was opened in another independent browser/device or the link was regenerated.
• Duplicate voter appears: confirm the Microsite attendee email matches the intended Vote voter. Alby normally reconciles matching Microsite/direct access to one voter identity and blocks new duplicate voter emails.
• Results do not appear: public results and participation remain withheld until the question closes.
• Facilitator or Who Voted is unavailable: these authenticated display pages require the Vote event itself to be Active.
• Embed does not load: confirm the Microsite page, project and Vote product are all available.

Prerequisites

• An Alby account and plan with Zoom Element access.
• Permission to manage the Alby account and Microsite page.
• A Zoom account authorised to use the meeting.
• The Zoom meeting ID and passcode where required.
• The associated Zoom host/user must be present in the meeting before external-account attendees can join through the embedded element.

Adding the App: connect Zoom to Alby

1. Sign in to Alby and open the required Account.
2. Open Account Settings → Integrations.
3. In the Zoom card, select Connect Zoom account.
4. Alby first shows an account-choice page. Zoom always uses the Zoom account currently active in that browser, so open Zoom and switch accounts first when the wrong account is active.
5. Return to Alby, select Continue to Zoom, then review the permissions requested by Alby.
6. If Zoom allows the app immediately, approve the connection. Zoom returns you to Alby.
7. Confirm the connected Zoom account is shown, then use Test connection.

If Zoom requires administrator approval

Some Zoom organisations require every Marketplace app to be approved by a Zoom account owner or administrator before a member can connect it. In this case Zoom displays a message saying the app needs pre-approval.

1. The user completes the Zoom request screen. A status such as Pre-approval requested or Waiting approval confirms the request has been submitted.
2. The user sends the request to the Zoom owner or administrator who controls Marketplace permissions for that Zoom account.
3. The Zoom owner or administrator signs in to the Zoom App Marketplace.
4. At the top right, select Manage.
5. Under Admin App Management, open App Requests, then open the active request for Alby.live Microsite Integration.
6. Approve the app for the requesting user, an authorised user group, or all users on the Zoom account, as appropriate.
7. The original user returns to Alby → Account Settings → Integrations and selects Connect Zoom account again to complete authorisation.
8. Once connected, use Test connection in Alby.

Usage: add a Zoom meeting to a Microsite

1. Open the Microsite Page Builder.
2. Add a Zoom element from the Elements menu.
3. If the account is not connected to Zoom, Meeting ID, Passcode and Fallback URL are read-only in Page Builder; connect Zoom under Account Settings → Integrations first.
4. Once connected, enter the meeting ID and passcode, and review the fallback URL, join label and display settings.
5. Choose the default attendee view: Gallery, Speaker or Active view.
6. Leave Hide attendee Zoom view selector enabled when attendees should not change the view.
7. Resize and position the element for desktop, tablet and phone layouts.
8. Save, preview and publish the page.
9. Start the meeting from the connected Zoom account before testing the public Microsite page.

The meeting joins automatically when the public page loads and the required attendee identity is available. If the meeting has not started, Alby shows a waiting message rather than a blank element.

Attendee experience and Zoom panels

• The meeting video stays inside the Zoom element.
• Zoom’s native Chat, Participants, Settings, Invite and Reactions panels can float above the page when opened.
• There is no separate Zoom Panels Page Builder element.
• Gallery, Speaker and Active view are the supported attendee view choices.
• Ribbon and Minimized views are not offered in Alby.
• Screen sharing is fitted within the meeting area and the Zoom toolbar remains available according to the meeting state.

Removing the App

Disconnect from Alby

1. Open the Alby Account and go to Account Settings → Integrations.
2. Find the Zoom card.
3. Select Disconnect Zoom and confirm.

Alby attempts to revoke the Zoom authorisation, then removes the encrypted access and refresh tokens and the local Zoom connection record. Existing Microsite layouts remain, but their Zoom elements cannot create authenticated joins until another Zoom account is connected.

Remove from Zoom

1. Sign in to Zoom and open the Zoom App Marketplace.
2. Open Manage → Added Apps.
3. Find the Alby app and choose Remove.

For the published production app, Zoom sends Alby a signed deauthorisation notification. Alby uses it to delete the matching stored Zoom connection data.

Zoom data handled by Alby

Alby stores the minimum connection information needed to identify the authorised Zoom user, refresh the connection and request meeting-join authorisation. OAuth tokens are encrypted at rest. Disconnecting or receiving a valid production deauthorisation notification removes the stored connection tokens and associated Zoom connection record.

See the Alby Privacy Policy for broader information about account data and retention.

Zoom troubleshooting

• App needs pre-approval: ask the Zoom owner or administrator to approve the request under Zoom App Marketplace → Manage → Admin App Management → App Requests, then connect again from Alby.
• Only “Waiting approval” is shown: this is the requester view, not the admin approval screen. The requester cannot approve their own request.
• Admin cannot see App Requests or approval controls: confirm they are signed into the Zoom account that controls the user and have owner, admin or Marketplace-management permissions.
• Connection test fails: disconnect and reconnect the Zoom account, then test again.
• Zoom keeps using the wrong account: Zoom reuses the account currently active in the browser and does not offer Alby a supported force-login parameter. Open Zoom, use the profile menu to switch accounts or sign out, return to Alby and retry the connection.
• Meeting not started: the associated Zoom host/user must join the meeting first.
• Invalid meeting ID or passcode: re-enter the values from the Zoom meeting invitation.
• Callback error: confirm the request started from the correct Alby environment and that cookies are allowed.
• Zoom element missing publicly: confirm the Microsite page is published and the project is Active.
• View selector missing: check the element’s Hide attendee Zoom view selector setting.
• Old connection still displayed after Zoom revocation: use Test connection, then Disconnect and reconnect from Alby.

For additional help, visit Alby Support.