Power User and Productivity

Bulk participant operations and CSV import

Move twenty, fifty, or a hundred participants in and out of a session in a few clicks rather than one at a time.

Adding one participant to a session is two clicks. Adding fifty becomes a chore unless you bulk-act. Gleo gives you three accelerators on the Participants tab: CSV import, bulk row actions, and suggested members from the playbook team. Combined, they take participant set-up from minutes-per-session down to seconds-per-session.

Video walkthrough — coming soon

The three accelerators

CSV import

Upload a spreadsheet of participants — emails, names, optional role — and add them all in one go. Best for one-off events with external attendee lists.

Bulk row actions

Select multiple participants in the table and apply a role change, status change, or removal to all of them at once.

Suggested members

Quick-add anyone already on the playbook team to this specific session — one click per person, no typing.

CSV import

The fastest way to seed a participant list when you have it sitting in a spreadsheet — an event registration form export, a customer mailing list, an internal contacts file. Gleo accepts a CSV with email as the only required column; everything else is optional.

What goes in the CSV

Column Required? Notes
Email Yes The unique identifier. Must be a valid email format.
First name No Used as the display name if the participant doesn't already exist in your workspace.
Last name No As above.
Role No One of Participant, Observer, Facilitator. Defaults to Participant if not specified.

The import flow lets you map your CSV's columns to Gleo's fields, so your headers don't need to match exactly — Email Address, e-mail, and EMAIL all map to the email field.

What happens to existing members vs new emails

  • Existing workspace members are added to the session straight away with the role you specified (or Participant by default).
  • New emails are added as session participants. They'll be invited to sign in (or complete prep as a guest — see Sharing prep links with non-members) when they receive the prep invitation.

What happens to invalid rows

Validate emails before you import. Gleo will skip any row with an invalid email format and surface the skipped rows in the import summary at the end of the upload. Nothing breaks — but if you don't read the summary, you might think you imported 50 rows when you actually imported 47.

Bulk row actions

Once participants are in the table, multi-select unlocks a row-action menu:

  • Change role — promote a batch of Participants to Facilitators, demote Observers, etc.
  • Remove — drop a batch of participants from the session.
  • Resend invite — re-trigger the prep invitation for participants who didn't get it the first time.

Select rows with the checkboxes on the left of each row, or Select all at the top. The action menu appears once one or more rows are selected.

Suggested members

If your playbook has a Team, Gleo suggests its members as one-click adds at the top of the Participants tab. This is the right shortcut for recurring sessions inside an ongoing engagement — the team's already on the playbook, so you don't need to retype their emails for every session.

The suggestion list updates whenever the playbook team changes, so onboarding a new team member to the playbook automatically makes them a candidate for every future session.

Walkthrough

  1. 1

    Open the Participants tab

    From a session, open the Participants tab. The current participant list, the suggested-members panel, and the Import CSV action are all here.

  2. 2

    Quick-add the playbook team

    If suggested members are showing, click each one to add them. (Most recurring sessions can stop here.)

  3. 3

    Import the CSV

    Click Import CSV. Drop in your file. Confirm the column mapping (email is required; others are optional). Click Import.

  4. 4

    Read the import summary

    The summary tells you how many rows were imported, how many were skipped (and why), and how many existing members were re-added. Don't dismiss it without scanning.

  5. 5

    Bulk-edit the imported rows

    Select rows with the row checkboxes (or Select all). Apply a bulk action — e.g. promote a batch to Facilitators or resend an invite. The action runs against every selected row.

Tips & pitfalls

Use suggested members first, CSV only when you have to. The suggested-members panel is friction-free; CSV import involves a file and a mapping step. For recurring sessions, the team is usually the participant list — start there.

Validate emails in the spreadsheet first. A 30-second sanity check in Excel or Google Sheets is faster than chasing down which rows Gleo skipped.

Pick the right role at import time. Setting role per row in the CSV is one keystroke; bulk-changing it after the fact is several clicks. If your CSV mixes Participants and Observers, set the Role column rather than importing them all as Participants and re-classifying.

Related pages