InnerWeb
Skip to main content

Group guest invitations: limits, order and implementation notes

A single group invitation request covers at most 144 addresses, and the limiter allows 5 requests per 13 minutes per user. The coordinator of an open day must therefore spread the sending over time and plan what the secretariat will receive, because a group invitation does not create accounts and the guest registers on their own.

144
addresses in a single group invitation request
Source: internal card
720
addresses at most in a 13-minute window (5 times 144)
Source: example calculation from the limits
13 dni
after this time the print order expires
Source: internal card

For whom and when to use group invitations

Group invitations are a tool for the coordinator who invites a group: an open day, a visit by a customer delegation, training for contractors, an external audit. The Invite multiple guests window works in three steps: paste the addresses, preview, send. This makes it possible to send dozens of invitations without entering each person separately.

The implementation notes concern three areas: the limits, what the system does and does not do after sending, and the impact on the secretariat, which handles the printing of labels.

Limits and how to fit within them

A single request covers at most 144 addresses. The limiter allows 5 requests per 13 minutes per user. In practice, one coordinator can send invitations to at most 720 addresses within 13 minutes (5 times 144), if the list is split into equal batches. For a group larger than that, the sending must be spread over further windows, or a second coordinator must be involved, who has their own limit.

We recommend not using the limit to the full. Keep one request in reserve for corrections, for example missing addresses or a typo fix. Sending in batches of about 100 addresses leaves a safety margin and makes the preview easier to check.

  • A batch of up to 144 addresses per request.
  • At most 5 requests in a 13-minute window per user.
  • Theoretical maximum in the window: 720 addresses (calculated from the limits).
  • A larger group: a further window or a second coordinator.

Capacity of group invitations in a 13-minute window

Capacity of group invitations in a 13-minute windowBar chart: 144, 432 and 720 addresses for 1, 3 and 5 requests in a 13-minute window.0200400600800addresses1 request: 144 addresses1441 request3 requests: 432 addresses4323 requests5 requests (limit): 720 addresses7205 requests (limit)
Source: Example calculation: limit of 144 addresses per request and 5 requests per 13 minutes

What a group invitation does and does not do

A group invitation does not create accounts or activation links. The guest registers on their own in the portal, which leaves one entry point into the access request process. This simplifies control: there are no two paths for creating accounts, and no accounts are created for people who never come.

The consequence for the coordinator: on the day of sending there are no badge IDs yet. Only after the guests register can the system print the labels. That is why the coordinator should send the invitations in advance and set a deadline by which the guests should have registered.

Print order in a group invitation

The field Send QR label print order appears only when the administrator has set the secretariat address. In a group invitation the order is sent only after the guests have registered. When only part of the group has registered, the system waits up to 8 hours, checks the queue every 5 minutes and cancels after 13 days.

As a result, the secretariat does not receive dozens of emails at the moment of sending, but a single order once the registrations have been collected. The print page accepts up to 144 badge IDs, so one group fits on one sheet.

Plan for a large open day

Send the invitations in batches a few days in advance. On the day before the visit, check how many guests have registered. In the morning of the visit the secretariat prints the labels from a single order. Guests who register later will appear in the next order.

Traps and how to avoid them

The first trap is pasting a list without checking the preview. The preview step exists to catch typos and duplicates before sending, and once the invitations are sent they cannot be recalled. The second is sending the whole group in one request without leaving any margin of the limit. The third is expecting accounts to be created automatically.

The fourth trap concerns communication: a guest who does not register in time will not appear on the print list. It is worth sending a reminder to those who did not finish their registration, the day before the visit.

Example calculation

How many invitations one coordinator can send

Assumptions
ParameterValue
Addresses in one request144 addresses
Requests in the window5 requests
Length of the window13 minutes

Result: 5 times 144 gives 720 addresses in a 13-minute window per user.

Note: Example calculation based on the limits from the function documentation; the actual capacity depends on the instance settings.

Video

Frequently asked questions

Does a group invitation create guest accounts?

No. The guest registers on their own in the portal, which leaves one entry point into the access request process.

When will the secretariat receive the print order?

After the guests register. When only part of the group has registered, the system waits up to 8 hours, checks the queue every 5 minutes and cancels after 13 days.

What do I do with a group larger than 144 people?

Split the list into batches of at most 144 addresses and send them in 13-minute windows, or involve a second coordinator with their own limit.

Plan the open day without flooding the secretariat

Book a talk about group invitations. We will spread the sending within the limits and set up the print order.

Let's talk