Join a session and invite guests

People join a SprintPoker session in two ways. Members of the workspace open it from SprintPoker or with the session’s Laya.net link. And while the session’s Guest access is on, anyone else joins with the same link with just a name.

Members of your workspace

• A session set to Everyone in this workspace is listed in SprintPoker for every member. Opening one that is in progress and not private seats you as a participant straight away.
• A session set to Only people you invite isn’t listed for anyone else: people join with the session’s link.
• A private session lets in only the people in it, even when others can find it, whichever app it was created in. A member who isn’t in it sees Private session and, while it is in progress, Let me in: they wait until a moderator lets them in with Add them, or turns them away with Deny. A person can ask once every 30 minutes, so after Deny they can ask again 30 minutes after they asked.

Share the session’s Laya.net link

A moderator opens Invite in the session bar, Invite people in the session’s ⋮ menu, or the share icon on the session’s card on the SprintPoker overview. The dialog is called Invite people, or Sharing for a session that is also in SprintPoker for Jira; there, Share Laya.net link in the people list and the ⋮ menu opens it at the link. It has two tabs: Share holds the session’s Laya.net link, and Settings what it lets people do. SprintPoker for Jira’s Share shows the same link.

1. On Settings, turn on Guest accessA new session starts with it off, so only the members of your workspace can join. Turn it on, and guests join with the session’s Laya.net link and just a name.
2. On Share, press Copy beside Laya.net linkOne line under it says who it lets in now: Guests can join with this link. or Only your workspace members can join. Open opens it, and QR code shows a code to scan.

The link stays the same for the whole session: there is nothing to replace or revoke. Turning Guest access off removes the guests in the room at once and stops new guests joining; their results are kept. External links sent before still work: they open the session’s Laya.net link.

Guests: joining with just a name

While Guest access is on, someone with the session’s Laya.net link can join without an account. Signed out, the link opens on the join card: they type a name (up to 40 characters, which everyone in the session sees), choose Vote or Just watch, pass the human check and press Join, or sign in below it. Signed in but not in the session’s workspace, they press Join as guest first. A guest joins that one session only: they aren’t added to the workspace and can’t see anything else in Laya.net.

With Ask before letting people in on (or in a private session), they pass the same human check, press Ask to join instead and wait until a moderator lets them in; moderators read Asked to join as a guest from the session link. under their name. The address of the session’s room in the workspace leads to the same page. While guest access is off, the page says This session isn’t open to guests.

• Guests see each item’s key and title (a typed-in item’s title), and its description when the host shares descriptions and no Jira admin shows guests the key and title only.
• A Jira issue’s description shows as it does in Jira, for guests as for members: its headings, lists, checklists, links and the rest of its formatting, and its pictures where Laya.net can read them for guests (through the workspace’s own Jira connection, or SprintPoker for Jira in its latest version). A mention shows the person’s name only.
• A laya.net card’s description shows as its board shows it, for guests as for members, with its links and the pictures in it.
• A Jira issue’s description is read live from Jira when a guest views it, through the workspace’s own Jira connection or SprintPoker for Jira (never through Laya Board for Jira alone), and never for an issue under issue security or in a project the site restricts. Where nothing can read the site for guests, they see its key and title only.
• Where no Laya.net Jira connection can read the site for guests, SprintPoker for Jira reads the description, and the pictures in it, for them, on any site where it is installed: Laya.net asks for it when a guest looks and keeps none of it. It turns on by itself and follows the Jira admin’s guest settings.
• Guests also see each issue’s comments, with each author’s name, and its assignee and reporter, by name, unless the host turns them off or a Jira admin doesn’t allow them. These are read live through the workspace’s Jira connection only, so they need one that can read for guests: SprintPoker for Jira’s reading for guests covers descriptions alone.
• When nothing here can read what a session shares for its guests, the guest settings say so in one line, and Preview as guest lists it as hidden.
• Guests see the board’s Reference Issues and Matching Issues by key and title (a reference’s assignee too, when the assignee and reporter are shown).
• Never shared with guests: attachments outside a description, email addresses, the room’s own links into Jira or the board, or the board itself.
• Guests vote; the moderators choose the final estimates.

Guest settings

A workspace admin can set other defaults for the workspace in SprintPoker settings. Create Session starts from them and says so under each switch they set; the session gets the switches as you leave them. In a session, only the host can open things up further: let guests in or let them vote, show descriptions, comments or the assignee and reporter, or stop asking before letting people in. Any moderator can narrow them. Preview as guest shows a moderator the session exactly as a guest sees it.

The lobby: letting people in

With Ask before letting people in on, guests and people from outside the workspace wait on a page that asks them to keep it open until a moderator lets them in. Members of the workspace go straight in.

For a session created in SprintPoker for Jira, the workspace is the Jira site’s Laya.net workspace. A private session holds everyone it doesn’t include, whichever app it was created in and whatever this switch says: guests, people from outside the workspace and members who aren’t in it all wait. Moderators read Tried to join but isn’t included in this private session. under a member’s name, with Add them, which lets them in; anyone else gets Let in. A guest a moderator lets in takes their seat.

In the room, moderators see who is waiting to join, with Let in and Deny, and Let everyone in when several people are waiting. It opens in front of the room the moment someone starts waiting; once closed, it stays as a banner under the session bar until nobody waits, and the next person to ask opens it again. A request nobody answers expires after 30 minutes, and the person can ask again with the same link. Someone who presses Cancel while waiting withdraws the request: it leaves the list at once, in both apps.

Join with an account

• Signed out, the session’s link offers Sign in to Laya.net and Create an account (under the guest form while guest access is on), and brings you back to it. A member of the session’s workspace then goes straight into the room; anyone else can join as a guest while guest access is on.

Coming back to a session

• A guest who opens the link again in the same browser goes back to their seat. After Leave session, Join again joins as a new person.
• A guest can keep their votes with an account: the room offers to sign in or create an account and keep the seat. On another device they would join as a new person.
• A guest’s access ends after 8 hours without activity. When the session ends, a guest’s results page stays open to them for seven days, in the same browser.