Product

Security and Identity

Every request carries an identity. An agent does not get a wider door than the person who asked. Access, isolation, and credentials are decided here before work reaches a model or a tool.

From capability to everyday work

Security and Identity, in practice.

Every request carries an identity. An agent does not get a wider door than the person who asked. Access, isolation, and credentials are decided here before work reaches a model or a tool.

Use it for
Buyers reviewing access boundaries and human oversight before adopting AI for operational work.
Start with
Define the pilot team, project membership, accounts to connect, and actions to review.
Read the setup guide
Illustrative workflow Sample data
The request

“Check the access and review points for a customer follow-up workflow.”

  1. Workspace and project membership define access to the work.

  2. The agent needs an account the caller owns or can use through sharing.

  3. Safe mode pauses integration actions that are not pre-approved.

Access before action

Example output
People
Workspace and project membership
Tools
Owned or shared authorized connections
Oversight
Action review and execution records

Identity & access

Members, roles, and permissions

People join a workspace by invite. Admins manage members, roles, and groups. Projects and topics have their own membership, so a finance project does not automatically open to the whole company.

An agent runs with the permissions of the person behind it. Optional SSO and MFA go through your identity provider. Sensitive actions stay reviewable.

How Kluff handles security

Workspace isolation

A separate environment per company

A workspace is one company: its people, projects, topics, agents, and connected tools. Work in one workspace stays in that workspace. Another company on Kluff does not share the environment, memory, or secrets.

If you belong to more than one company, you switch workspaces. Billing, team, and audit history belong to the workspace you are in, not to a shared pool.

Trust and data handling

Encrypted secrets

Credentials applied at runtime, never in chat

Integration tokens and other credentials live as encrypted secrets. Agents and flows receive them when a tool needs them. They should not appear in a prompt, a thread, or a canvas.

Rotate a secret from Settings if it leaked elsewhere. Prefer secrets over dropping API keys in chat.

Trust and data handling

Before you try it

Questions for your evaluation.

Buyers reviewing access boundaries and human oversight before adopting AI for operational work.

Define the pilot team, project membership, accounts to connect, and actions to review.

Integration safe mode, MCP connection trust, and canvas access are distinct controls. Review each path used by your workflow.

Unlimited inference.
Company memory.

Connect your tools, ask your first question in a project, and watch memory, spend, and visibility stay in one place—not scattered across personal chats.

$15 / user · Unlimited AI
Q4 launch› Launch dashboard
Sara Castillo

@kluff build a launch dashboard from HubSpot and the Q4 budget sheet. Refresh it every morning.

Kluff

Done. Signups come from HubSpot, spend from the Q4 budget sheet. It refreshes at 7:00 AM.

v2 adds the channel split you asked for.

Maya Ruiz

Can we flag any channel over $40 per trial?

Kluff

Added. Paid social is flagged.

Q4 launch dashboard
Q4 launchHubSpot + Q4 budget sheet · refreshed 7:00 AM
Live
Signups1,284+18% vs last week
Trials started31224% of signups
Spend$8,420of $12,000 budget
Daily signups
MonTueWedThuFriSatSunMonTueWed
Send the renewal to Harbor Foods?

It sends from your Gmail, as you, with the draft attached. Nothing else leaves the project.

SENDGmail · Dana Reyes, Harbor Foods purchasing
ATTACHGoogle Drive · Harbor renewal 2026.docx
Finance check done

Ana Chen confirmed net 45 at 9:18 AM. Your rule: every customer email waits for you.

Sent · logged to the project