08 / For business

Your team.Your directory and drive.

Invite the colleagues who need to send, approve, or look something up. Give each person a role, search your existing staff directory when addressing a send, attach from your company drive, and switch between organisations under one login.

Roles and groups · your own staff directory · your company drive · multiple organisations

In the app

One organisation

Northbridge Bank · 14 people

  • Who can send the operations desk, six people
  • Who approves two named directors, quorum of two
  • Where files come from your own drive, at the moment of sending
  • What we store about your staff nothing you did not explicitly invite

  1. Invite

    You add people by role, not by handing out keys

    Four roles: the administrator, the developer who holds the keys, the operations desk that does the sending, and view only. Somebody who can draft is not somebody who can approve, and neither of them needs the keys. A new starter gets what the job needs on their first day and nothing else.

  2. Search

    You find a colleague without giving us your staff list

    We query the staff directory you already run, at the moment you type, with your own sign-in and your own permissions, and the results are gone when the search is. There is no nightly job copying your directory into our database, because there is no copy.

  3. Switch

    You run more than one organisation from one login

    A group with several entities, an agency acting for clients, a bank and its microfinance arm. Switch between them the way you already switch between businesses on a payments dashboard.

We never copy your staff list. We look, at the moment you ask, and then we forget.

How the directory works
Searched live against your own provider, with your sign-in, at the moment you type.
What we keep
A row for each person who has touched Keepable. Nothing about the rest of your staff.
Files from your drive
Attached at the moment of sending, from your storage, under your permissions.

The detail

What are the four roles allowed to do?
An administrator runs the organisation, including who else is in it. A developer holds the API keys. Operations does the work: drafting, sending, and answering desks. View only reads. Funding the wallet is an administrator's act and deliberately not something a key can do at all.
If I demote somebody, when does it take effect?
On their next request. The role is read live rather than stamped into their session when they signed in, so it does not wait for a token to expire. That is the difference between a control and a delay.
What can an API key do that a person cannot, and the other way round?
A key sends, reads and rotates itself. It cannot accept the sender agreement, submit your company's paperwork, change who sits on an approval desk, mint another key, or disconnect your identity provider. Those need a person, because a record reading "key kp_live_5179 accepted your terms" is not evidence that anybody accepted anything.
What exactly do you store about my staff?
A row for each person who has actually touched Keepable: invited by email, signed in through your identity provider, or picked from a search and activated on their first sign-in. A directory search result is held for the length of the search and never written down. There is no nightly job, no mirror, and nothing to go stale or to leak.
And the files on our drive?
Browsing your storage returns results that are equally ephemeral. A file is read at the moment you attach it to a send, under your own permissions, and there is no watch-this-folder option anywhere in the product because there is nothing watching.
We run several entities. Is that one login or several?
One. A group with several companies, an agency acting for clients, a bank and its microfinance arm: you switch between them the way you already switch businesses on a payments dashboard, and your role is per organisation rather than per login.

The limit

This is not a sync, and that is the point. Nothing here mirrors your directory, so there is nothing to leak and nothing to go stale, and equally a colleague who has never signed in cannot be found until they do. That is the trade, we made it deliberately, and we would make it again.

Start here

Gbìyànjú rẹ̀

For developers: Connections reference.