Skip to content

Secure your workspace

Freesbe’s defaults are safe for most teams, but a few settings are worth deciding on deliberately, especially when your team talks to customers all day. Work through this list once when you set up the workspace, and again when your team or your customers’ expectations change. Everything here is in Workspace settings → Security & compliance unless it says otherwise.

Workspace settings, Security & compliance, Sign-in: single sign-on and multi-factor authentication

If your company already uses Google Workspace or Microsoft 365, require it. Then people sign in with the accounts your IT team already manages, under its rules for passwords and second steps.

  • Open Single sign-on and under Members must sign in with, choose Google, Microsoft or Google or Microsoft.
  • Sign in with that provider yourself first. Freesbe won’t let you lock yourself out.
  • Requiring single sign-on comes with the Corporate and Enterprise plans.

Workspace settings, Single sign-on: Members must sign in with

SSO decides how people sign in, not who joins: people still need an invite. See Single sign-on.

Passwords get reused and phished. Requiring multi-factor authentication means a stolen password alone doesn’t open your workspace.

  • Switch on Require multi-factor authentication. It comes with every paid plan.
  • Pick how often under Ask again. Every day is a good balance for most teams; choose Each time Freesbe opens if people share computers.
  • Signing in with a passkey, Google or Microsoft counts as the second step by itself, so people who use them see no extra prompt when they sign in.

Workspace settings with Require multi-factor authentication on and Ask again set to Every day

Encourage everyone to add a passkey or set up Approve on your phone: it’s quicker than typing codes. See Multi-factor authentication.

Out of the box, members can share any file and guests can share anything except programs and scripts. Freesbe checks every upload by its name and by what’s inside, so a program renamed to report.pdf is still caught.

  • If your team never needs to send programs, set Files from members to Anything except programs and scripts too.
  • For guests, consider Only the kinds I pick, with just Documents and Images.
  • On Corporate and Enterprise, add Always allow for the odd file type your partners send, like dwg, and Always block for anything you never want, like zip.

Workspace settings, Security & compliance: File types, with members blocked from sharing programs and scripts

See File types.

Guests only see the channels they’re invited to and the people in them. To stay in control:

  • Leave Ask people in #channel to approve each guest before they join on when inviting, so someone checks each person first.
  • Make one channel per customer or partner, like #acme-rollout, rather than adding guests to internal channels.
  • When a project ends, Deactivate the guest in Workspace settings → People → Members.

The Invite people outside Northwind dialog, with the approval option turned on

See Guests.

Let people ask to control shared screens is off by default. Turn it on only if your team helps customers or each other by taking control of a screen. The person sharing always decides, every time, and Recent sessions shows the last 100 requests: who asked, whose screen and how long it lasted.

The Remote control switch and the Recent sessions log

See Remote control.

  • Deactivate people who leave in Workspace settings → People → Members. They’re signed out at once, their messages stay, and their webhooks and phone device are turned off.
  • Revoke invite links you no longer need in Workspace settings → People → Invites.
  • Ask everyone to check Preferences → My account → Sessions and apps → Your sessions now and then, and sign out of anything they don’t recognize.

Your sessions: Chrome on macOS (this device), Freesbe for Windows and Safari on iOS, each with a Sign out button