Why sessions need roles
A congress abstract rarely has one author. A typical abstract names five or six people: the PhD student who will present it, the supervisor, and colleagues from the lab and the clinic. They are all authors, and all of them must appear in the Book of Abstracts. But only one of them presents the abstract at the congress, only that person needs to confirm that they will come, and only that person belongs on the agenda card. A session block, on the other hand, has one or two chairs who lead it but do not present.
run.events tells these people apart with session roles. A session role is the part a person plays on a session: presenting author, co-author, chair, or any other part you define. Every person on a session holds exactly one session role.
The roles of an event
Every event starts with one session role: Speaker. It is the event's default role, it always counts as a speaker, and it cannot be deleted. Many events never need another role. A scientific congress usually adds at least Presenting author, Co-author and Chair.
You manage the roles on the card Session roles on the Content And Speakers page, under Configure. Add new creates a role. Choosing a role opens its fly-out, Edit session role, with its settings.
What the settings of a role decide
Each setting answers one question about the people who hold the role.
- Counts as a speaker: are they speakers? If ticked, they appear in the speaker lists and have a speaker profile, and once their session is accepted they are asked to fill in the speaker agreement, if the presentation type has one. A presenting author counts as a speaker. A co-author who does not present usually does not, and neither does a chair.
- Must confirm the session: do they have to confirm that they will come, once the session is accepted? Tick it for the presenting author. Leave it off for co-authors, or every co-author will receive a confirmation request.
- Default role: is this the role that is preselected when someone is added to a session? Exactly one role per event is the default.
- Display: how does the public see them? Full shows them as speakers, with their profile. Short lists them on one line under the role's name, for example "Co-authors: Anna Müller (University of Vienna), Ben Schmidt". Hidden does not show them at all.
- Session owners may add people in this role: can the person who submitted the session add people in this role? The session owner is the person who submitted the session. With Send them an invitation to accept, each person they add must accept before joining the session. Without it, the person is added at once.
- Submitters may take this role themselves: can the person who submits choose this role for themselves? Tick it on Presenting author, so that an author who will present can say so while submitting.
- Affiliations: must they give their institution? Not asked, Optional or Required. This setting only works while the event uses affiliations (see ORCID iDs and Affiliations). While affiliations are off, the setting says so and cannot be changed.
- Receives session mails: do they receive the mails about the session, such as the decision mail?
- Can moderate questions: can they approve and answer the questions the audience sends during the session? This is usually ticked on Chair.
- Manages the session block's programme and The organizer approves the chair's changes: the rules for chairs, explained further below.
A role also has a colour and an icon. They mark the role on the people of a session, so you can see at a glance who presents and who co-authored.
Each presentation type uses its own roles
An event's roles are a list to choose from. Each presentation type then says which of these roles its sessions use, and how many people may hold each one. You set this on the presentation type's tab Roles: open Presentation Types, choose the presentation type, and open the tab Roles.
Each role on the tab has a Min and a Max. For an oral presentation, for example, Presenting author might have Min 1 and Max 1, so every abstract has exactly one person who presents it, and Co-author might have Max 12 and no minimum. An empty field means no limit. Add role adds another of the event's roles to the presentation type. Remove takes a role off it, but the last role cannot be removed. A new presentation type starts with the event's default role only.
The submission offers only the roles of its presentation type. If a role exists in the event but the author cannot choose it, check that the presentation type lists it.
What happens when someone breaks a rule
When a speaker's own change would break a minimum or a maximum, run.events refuses the change with a sentence that names the rule, for example: "Oral presentation allows at most 1 Presenting author." The speaker can then correct the people of the session. Your own changes as organizer are not limited: you can always fix the people of a session, even if the result breaks a rule for a while.
What the author sees
Authors can add other people to a session only when the event allows it: tick Allow Multiple Speakers Per Session in Call for Content Settings on the tab Speakers and messages. When an author submits, they then add the other people of the session in the role each one plays: themselves as presenting author, their supervisor and colleagues as co-authors. They can pick from people they have worked with before, so a returning author does not type the same co-authors again. They can also put the authors in order, because the order of the authors matters on the abstract and in the Book of Abstracts.
Chairs
A chair leads a session block at the congress: they introduce the speakers, keep the time and lead the discussion. In run.events, the chairs of a session block hold a session role, usually named Chair. You add them on the block's tab Chairs in the Agenda Builder.
Two settings of the chair's role decide how much the chairs can do before the congress:
- Manages the session block's programme: the chairs manage their block. They receive an invitation, and once they accept, they find the block in the speaker portal under Session blocks you chair, as soon as the block is placed on the agenda. There they can put the talks in order, set their lengths, take talks out, take accepted sessions on the block's topics, and fill the block's placeholders. They can do this until the date in Chairs can change their blocks until, in Call for Content Settings on the tab Call and deadlines.
- The organizer approves the chair's changes: the chairs' changes are a draft until you approve them. The chair sends the changes with Send to the organizer, and you decide each part in the panel Chairs' changes in the Agenda Builder. Without this setting, the chairs' changes go into the draft of the agenda directly.
Either way, the chairs' changes reach the public only when you next publish the agenda. The article Session Blocks, Placeholders, Guided Poster Sessions and Chairs explains session blocks and chairs in full.
An example: the roles of a medical congress
| Role | Counts as a speaker | Must confirm | Display | Typical use |
|---|---|---|---|---|
| Presenting author | Yes | Yes | Full | The author who presents the abstract |
| Co-author | No | No | Short | The other authors of the abstract |
| Chair | No | No | Full | The people who lead a session block; with Receives session mails, Can moderate questions, Manages the session block's programme and The organizer approves the chair's changes |
The oral presentation then uses Presenting author (exactly one) and Co-author (up to twelve). The poster uses the same two roles. Session blocks use Chair.
Two common mistakes
- Co-authors receive confirmation requests and appear as speakers. On the role Co-author, clear Counts as a speaker and Must confirm the session.
- Authors cannot choose a role, although it exists. Each presentation type lists its own roles. Add the role on the presentation type's tab Roles with Add role.
Related articles