Security

Who gets in, and what stays private.

People sign in once, through your identity provider, with a passkey or with a code sent to their work email, under a policy your admins set. Roles decide what each person can use and see. Conversations stay with the person who had them, and every change to a plan names who made it.

Contact sales

No passwords: Single sign-on, passkeys, Google or Microsoft accounts, or an emailed code.
Your sign-in policy: Require single sign-on, cap how long a sign-in lasts, and grant exemptions with a reason.
Roles that reach the work: Down to the agent and the library in Pebbl AI, and to a single plan center in PebblPlan.
Private conversations: No screen, for your admins or ours, opens someone else’s.

Sign-in

One sign-in covers every Pebbl product your organization uses. Connect your identity provider over OpenID Connect; the connection stays off until a test sign-in passes. Then require single sign-on for everyone, with named exemptions for break-glass accounts: passkey only, with a reason, who granted it and, if you like, an end date.

Set how long a sign-in can last and when an idle one ends. A change that would lock out the admin making it is refused. Your email domain sends people to your sign-in page; it doesn’t let anyone in. Admins invite people, and nobody joins just by signing in.

Email codeA one-time code sent to the person’s work address.
PasskeyThe face, fingerprint or PIN the device already uses.
Google or Microsoft accountThe account the person already uses for work.
Single sign-onYour identity provider over OpenID Connect, with a Microsoft Entra ID preset.

Sessions

Remove someone, and they’re out.

Every request is checked against a session held on our side. Suspend or remove a person, and their next request finds them signed out. Each person can see where they’re signed in and sign out everywhere else.

Separation

Your organization, kept apart.

Your organization’s ID is part of every record’s key, and every request is scoped to the organization in the person’s sign-in, never one the request names. Our tests sign in as another organization’s admin and try every route that takes an ID; a test fails if one gets through. Secrets are encrypted with keys that can be rotated, and passkeys keep only public keys.

In Pebbl AI

Agents, knowledge and private conversations.

Roles that reach the agent and the library.: Pebbl AI has 26 permissions. Start from the built-in admin and member roles, or make your own. Each role carries its permissions, which agents its people can use, and whether it can read every knowledge base. Nobody can grant a permission they don’t hold, and the last admin can’t be removed.
Libraries shared on purpose.: Each team owns its knowledge bases and grants access to roles. Before a library is attached to an agent, Pebbl AI shows how many people, which roles and how many documents that reaches. Agents read libraries; they never write to them.
Their conversations stay theirs.: A conversation belongs to the person who had it. What admins with billing access can see about use is who was active and how often, never what anyone asked. Memory comes only from what a person and an agent said to each other; people can switch it off, see what’s kept, and forget any of it.

In PebblPlan

Who can see what, and who did it.

Access down to a single plan center.: A grant covers the whole organization, one plan type, a group of models, a single model, or a plan center and everything beneath it. Budget owners read only what their plan center’s contracts provide, cut to their slice, and reviewers approve and reject without being able to edit.
Signed by whoever was signed in.: Every comment, approval, rejection and submission records the person who was actually signed in, and the agent they used. The server takes the name from the session, never from what the request says.
A history you can hand to audit.: Each version keeps every revision: what changed, who made it, through which agent, and when. Undo and restore write new revisions, so nothing is erased. A locked version takes no more writes, and locks don’t come off.
No standing access for our staff.: When PebblPlan support needs to look at something, they ask for 1 to 72 hours of access and say why. One of your admins approves or denies it, and the request and the decision go in your security log.

Agents

An agent is no wider than its person.

No wider than its person: An agent holds exactly the permissions of the person it works for, and every tool call is checked against them, the same as a request from the app.
Asks before it acts: In PebblPlan, before an agent submits, approves or rejects, locks a version or takes a close, it shows the person exactly what it will do and waits for their go-ahead.
Outside text is data: Text from documents and pages is never saved to memory or a knowledge base, replies don’t load remote images, charts can’t fetch anything, and the code sandbox has no internet access.
Tools start off: Code execution and web browsing are off for every agent until an admin turns them on for the jobs that need them.

Send us your security questionnaire.

We’ll answer it in writing, hosting and encryption included, and walk your IT and security teams through sign-in, roles and the audit trail in the product you’re looking at.