Skip to main content
When your whole company builds on Biscuit, the most important question is who can see what. Everything your team builds stays private to your workspace until someone decides otherwise, and access is controlled by the people who own each part of it. These rules are enforced on Biscuit’s servers, not written into each app by hand.

​
Private by default

Everything your team creates belongs to the space it was built in. A sales team’s CRM with its customers, deals, and uploaded contracts, is only visible to that team unless someone explicitly shares it or makes it public.

​
Three levels of access

Access follows the way your company is organized, so you can open something up for one team without opening it up for everyone.
  • Workspace: the workspace owner decides who joins your company’s workspace. Only owners can invite new members, everyone signs in through Biscuit’s authentication, and removing someone takes away their access to everything in it. See Members.
  • Space: the space owner decides who can reach a team’s apps, data, and files, and whether each person can use them or also edit them. Each space also has an access setting: Everyone, Open, Closed, or Private. See Spaces.
  • App: the app owner decides which people and spaces can use or edit a single app, and whether it’s public. People with Can edit access can publish new versions. See Sharing apps and Publishing your app.

​
Workspace

Only the workspace owner can invite new members. Everyone signs in through Biscuit’s authentication, and removing someone from the workspace removes their access to everything in it. See Members.

​
Space

Each space has an access setting (Everyone, Open, Closed, or Private) and its own members with Can use, Can edit, or Owner permissions. See Spaces.

​
App

Each app can be shared with specific people or whole spaces, with Can use or Can edit access. See Sharing apps.

​
Nothing is shared by surprise

Before an app reaches new people, Biscuit shows you what it depends on: which data it reads and which connected accounts it uses. You see this when you:
  • Share an app with a person or another space. See Sharing apps.
  • Move an app to a different space. See Moving apps.
Review this before you confirm, especially if the app reads data that only one team should see.

​
Data rules inside your apps

Access doesn’t stop at who can open an app. Inside every app, each data table has rules for who can create, read, update, and delete records.
  • No rule means no access. If a rule isn’t set, nobody can reach that data.
  • Rules run on Biscuit’s servers. Apps never talk to the database directly. Every read and write goes through Biscuit’s data layer, which applies your permissions before anything is saved.
  • Every change is checked. When the AI changes how your app stores data, a separate security review checks for exposed personal data and permissions that are broader than they should be.
  • Give each team its own space: Keep a team’s apps and data in its space, rather than in the shared space.
  • Use Private spaces for sensitive work: HR, finance, and leadership tools should live in spaces that others can’t find.
  • Share with Can use by default: Give Can edit only to people who maintain the app.
  • Keep the shared space for company-wide tools: Anything there is visible to everyone in the workspace.
  • Publish only what’s meant to be public: Websites, landing pages, and forms are fine. Internal tools are not.
  • Remove access when people leave: Removing someone from the workspace removes their access to every space and app.