Jump go the main content
Keepable
Pidgin
Menu

Your team. Your staff list and drive.

Invite colleagues wey need send, approve or check something, and give each person the right Workspace role. Keep company-mailbox authority as separate appointment, search your existing staff list when you address a send, and attach from your company drive.

Example to explain am

Northbridge Bank · 14 people

Who fit send
Operations desk, six people
Who dey approve
Two named directors, both must approve
Where files come from
Your own drive, when you dey send
Wetin we store about your staff
Nothing wey you no deliberately invite
Who fit act for the company
People wey get separate appointment to the company Keepable

Wetin you fit do with am

You add people by role, no be by giving everybody keys

Four roles: administrator, developer wey hold keys, operations desk wey dey send, and read only. Person wey fit draft no automatically fit approve, and neither need keys. New staff gets only wetin the job needs from first day.

You find colleague without giving us your staff list

We search your existing staff directory as you type, with your own sign-in and permissions. Results disappear when search ends. No nightly work copies your directory into our database, because we no keep copy.

You run more than one organisation with one login

Group with several companies, agency wey act for clients, bank and im microfinance arm. Switch between them like you already dey switch businesses on payment dashboard.

Your staff list dey searched live; we no copy am into Keepable.

How the staff list works

Live search through your provider, with your sign-in, as you type.

Wetin we keep

One record for each person wey don use Keepable. Nothing about your other staff.

Files from your drive

Attached when you dey send, from your storage, with your permissions.

Questions and answers

Wetin the four roles fit do?

Administrator runs organisation, including membership. Developer holds API keys. Operations drafts, sends and answers from desks. Read only reads. Only administrator fit fund wallet; key deliberately no fit do am.

If I reduce person role, when e go start?

From their next request. We check role live instead of locking am into session at sign-in, so e no wait for token to expire. The control takes effect, no delay.

Wetin API key fit do wey person no fit, and person fit do wey key no fit?

Key fit send, read and change itself. E no fit accept sender agreement, submit company papers, change approval-desk members, create another key or disconnect identity provider. Those need person: record wey say "key kp_live_5179 accepted your terms" no prove say person agree.

Wetin exactly una store about my staff?

One record for each person wey actually use Keepable: invited by email, signed in through your identity provider, or picked from search and activated on first sign-in. Search result stays only for the search; we never save am. No nightly copying or staff-list mirror for Keepable.

What about files for our drive?

Browsing your storage gives temporary results too. We read file only when you attach am to send, under your own permissions. Product no get any option to watch a folder.

We run many companies. Na one login or many?

One. Group with many companies, agency wey act for clients, bank and im microfinance arm: switch between them like businesses for payment dashboard. Your role dey per organisation, no be per login.

Workspace role lets person act through company mailbox?

No. Workspace role controls wetin colleague fit do for the organisation work area. To act through company own Keepable, person needs separate appointment. So permission to send, receive or reply for company dey clear and linked to the person.

The limit

Keepable no copy your staff list, and colleague wey never sign in no fit show until dem do. Workspace role no be company-mailbox appointment. Live search leaves your directory in your control, while company authority stays clear.

Use am for your organisation.

Keepable product screen

Real Keepable interface. Sample data.