What ending an open session actually does
An open session is a time-boxed collaboration window, not a permanent sharing state. If you started one for a temporary guest review or workshop and the work is done, you close the window rather than leaving it to expire.
FigJam open sessions let visitors collaborate for 24 hours on Professional, Education, Organization and Enterprise plans; an editor can end a session early from Share. Source
That framing matters for expectations. Closing the session ends the collaboration window; it is not a board deletion and it is not a blanket revocation of every collaborator. People with their own standing access keep what that access allows.
Step by step: close the session
- Open the FigJam file as an editor.
- Open the Share controls.
- Find the open session entry and choose the option to end it now. The reviewed source describes an editor ending a session early from Share; the exact control label and menu layout are not established by the approved facts, so confirm what your current version shows rather than assuming a fixed path.
- Record the time you ended it. This is your reference point for the access review below.
If the option is absent or greyed out, do not keep clicking. First confirm you are in an editor role on the file and that the plan is one of the eligible ones. If both hold and the control still does not appear, treat it as an unresolved interface question and check the current in-product help for your version.
Who keeps access after the session ends
The useful distinction is between people who were only in the session and people whose access comes from somewhere else.
After a session ends, visitors outside the team without an invitation lose session access, while existing view permissions can still allow viewing and copying. Source
So the review has two questions, not one: did the person rely on the session, and do they hold a separate permission? A visitor with no invitation and no other grant should be out. Someone who already had view access is a different case.
Ending an open session does not turn existing view permission into edit permission. Source
Ending the session removes the temporary editing route. Review each person’s standing permissions separately to determine what they can still do.
Access review checklist
After ending the session, review temporary visitors, invited collaborators and team members separately.
| Group | What to check | What to expect |
|---|---|---|
| Temporary visitors (no invitation, outside the team) | Whether they joined only through the open session | Session access ends; they should no longer get in through that route |
| People with existing view permission | Whether the file was shared with them before the session | Viewing and copying may still be possible under that permission |
| People with edit or other standing access | Whether they hold a role granted outside the session | Their existing permission is unchanged by ending the session |
| Team members | Whether the file sits in a team space they can reach | Team access is separate from the session window |
| Invited external collaborators | Whether an invitation exists independently of the session | Invitations are not the same thing as session participation |
Two limits are worth stating plainly. First, this checklist is about what the reviewed facts establish; it is not a full audit of every sharing route a file might have. Second, an empty or edited profile elsewhere tells you nothing about these permissions.
Failure paths to plan for
- A visitor says they can still open the file. Ask whether they received an invitation or already had view access. If neither applies, re-check that the session actually ended and that you are looking at the same file.
- A viewer can still copy content. That is consistent with existing view permission. If copying is the concern, the fix is to review that permission itself, not to end the session again.
- You expected editing to stop for everyone. Ending the session removes the session route to editing, but people with standing edit access keep it. Review those roles separately if that is your goal.
- You cannot find the control. Confirm role and plan first; do not assume the feature is broken or that the session is still running.
What this task does not cover
This is about closing a temporary collaboration window. It is not the same as changing who a Figma file link is shared with, and it is not account deletion. If your actual problem is a public creator credit or a published community file, that is a neighboring but different task: related account-control guide.
It is also not an identity check. A username search can surface public profiles that look related, but public matches are leads, not proof of ownership, and they do not control FigJam sharing settings, recover accounts, or confirm who is behind a handle. If your concern is what is publicly visible about an account name rather than who can open a board, the better next step is to review your public account footprint.
A short recap
End the session from Share when the temporary collaboration is over, then review access by group: session-only visitors, existing viewers, standing editors, team members, and separately invited collaborators. Expect view access to survive and expect no automatic permission change. For the wider method behind separating leads from proof, see the methodology and the FAQ.