10 / Fún àwọn àjọ

Your team.Your directory and drive.

Invite colleagues who need to send, approve or look something up, and give each person the right Workspace role. Keep company-mailbox authority as a separate appointment, search your existing directory when addressing a send, and attach from your company drive.

Workspace roles · groups · company appointments · your staff directory · your company drive

Nínú app

One organisation

Northbridge Bank · 14 people

  • Who can sendthe operations desk, six people
  • Who approvestwo named directors, quorum of two
  • Where files come fromyour own drive, at the moment of sending
  • What we store about your staffnothing you did not explicitly invite
  • Who can act for the companypeople given a separate appointment to its Keepable

  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.

Your staff directory is searched live and is not copied into Keepable.

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.

Kúlẹ̀kúlẹ̀

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 or mirrored staff directory in Keepable.
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.
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.
Does a Workspace role let someone act through the company mailbox?
No. A Workspace role controls what a colleague can do in the organisation's operational workspace. Acting through the company's own Keepable requires a separate appointment, so authority to send, receive or respond for the company is explicit and attributable.

Ààlà

Keepable does not mirror your staff list, and a colleague who has never signed in cannot be found until they do. A Workspace role is also not a company-mailbox appointment. Live search keeps the source directory in your control, while company authority remains explicit.

Bẹ̀rẹ̀ níbí

Ṣí Keepable Workspace

Fún àwọn olùdàgbàsókè: Connections reference.