2. Size, prefix, and duplicate entries

Under Format, set the participant count and entry message format. Representative and duplicate entry settings are on the same screen.

Entry size

By default, the message author counts as a participant. The entry is accepted only when the author plus uniquely mentioned users exactly match the configured size. Mentioning the same user more than once still counts as one user.

Entry size can be set from 1 to 50. The presets cover one to five participants; choose Custom to enter a value from 6 to 50.

With Distribute roles per member enabled, select exactly as many rotation roles as there are members, up to 50. After changing the entry size, adjust the role count to match before saving.

Trio example

The author mentions two other users.

Team Name: Sample Team
@member2 @member3

Prefix

The prefix identifies the line containing the team name. The current default is チーム名. The UI adds the separator automatically, so enter the prefix without a colon.

The prefix can contain up to 32 characters.

Both examples are accepted:

Team Name: Sample Team

Team Name：Sample Team

Text before the prefix prevents that line from matching, and an empty team name is rejected. User, role, and channel mentions, @everyone, and @here are removed from the resulting team name.

Blank prefix

When the prefix is blank, the first non-empty text line becomes the team name. Ordinary conversation can therefore be mistaken for an entry. Only use this mode in a dedicated entry channel.

Representative entry

When enabled, mention the same number of users as the configured entry size. The author is included when explicitly mentioned in their own message.

For example, a normal Duo entry contains the author and one mentioned user. With representative entry enabled, only the two mentioned users are included. Participant count validation, required-role validation, duplicate detection, role grants, and created-object permissions apply to those two users.

Team Name: Sample Team
@member1 @member2

Allow duplicate entries

The BOT detects an existing entry by checking whether a participant already has any configured shared or rotation role.

Important: When Allow duplicate entries is OFF, configure at least one shared or rotation role under granted roles. If neither is configured, the BOT cannot detect previous participants, so turning this setting OFF does not reject duplicate entries.

Team roles are not used for this duplicate check.

Keep an entry guide as the latest message

When enabled, the BOT posts an example at the bottom of the entry channel using the current entry size, prefix, and representative-entry settings.

After another message is sent, the BOT deletes the previous guide and posts it again so the guide remains the latest message. Updating the panel refreshes the example. Disabling the setting or deleting the panel removes the guide.

For a normal entry, the author counts as one participant, so the example shows one fewer participant mention than the configured entry size. With representative entry enabled, the example shows the same number of participant mentions as the configured size.

The BOT needs permission to send messages, read message history, and delete its own messages in the entry channel.