The database itself keeps each workspace's data apart from every other's, on every request. Here is how access, invitations, files and capture are protected, and the limits to know about.
Your workspace is walled off
Every record in Plum, from an account to a file, belongs to exactly one workspace. On every request, the database checks which workspace you're working in, that you're still a member of it, and that your role allows what you're asking for. It returns nothing from any other workspace, however the request is made.
Because the check sits in the database and not only in the screens, a mistake in the app still can't show you another workspace's data. A record also can't be moved to another workspace, or point at a record in one.
Automated tests try to read and change every kind of record across workspaces, including with forged and revoked sign-ins, and every change to Plum must pass them before it is merged.
Roles
Your role decides what you can see and change, and the database checks it too. Your role is read fresh on every request, so when someone is removed or their role changes, it takes effect at once, even if they're signed in.
Signing in
Plum has no passwords. You sign in with a link sent to your email address. A sign-in link only ever takes you to a page on Plum's own site.
Who can join your workspace
- By invitation. Only owners and admins invite, and only an owner can invite an owner. An invitation works once, only for the address it was sent to, and expires after 7 days. It can be withdrawn before then.
- By company domain. An owner or admin claims a domain and proves it by publishing a DNS record. Only then can colleagues with a confirmed address at that domain join, at the role chosen, which is never owner or admin. Public mail providers such as Gmail can't be claimed.
- Invitations are limited to twenty an hour per person and fifty a day per workspace.
Files
- Files are kept in private storage, in a folder that belongs to your workspace. Storage itself refuses access to any folder but your current workspace's.
- A file is handed out only through a download link that works for one minute, made for someone who can already see it.
- Files always download and never open inside Plum. Web pages, SVG images and scripts can't be uploaded.
Capture
- Your capture secret is stored only as a hash, a one-way fingerprint. Plum shows the secret once, when it is created, and can't show it again. Replacing it cuts off the old one at once.
- A note is accepted only with your workspace's secret, and only into your workspace.
- Captured email needs the mail provider's signature, and is accepted only from people in your workspace whose address the receiving mail server confirms is genuine.
- Full meeting transcripts are kept only if your workspace turns that on.
In your browser
Plum's pages run only Plum's own scripts and can't be shown inside another website. Pages with your data are built for you on each request and are never served to anyone else from a shared cache.
Limits to know about
- Uploaded files aren't scanned for viruses.
- Plum doesn't offer single sign-on (SAML) or custom roles.
- Anyone holding your capture secret can add meeting notes to your workspace, though they can't read anything back. Keep it in your automation tool only, and replace it if it may have leaked.