Skip to content
Docs

9 results

Get started

How Seren works

Seren combines Seren Employees with reusable skills, trusted knowledge, scoped access, and review controls. Teams work with Seren Employees as a product. The CLI, SDKs, and API expose the underlying agent platform concepts used to operate them.

Terminology

Employees are built on agent services

A Seren Employee is a managed coworker with a role, instructions, skills, connected knowledge, access policy, and operating history. A managed agent is the technical resource that runs this work. Product guidance uses Seren Employee for the product experience. Technical documentation uses managed agent for deployments, runs, identities, grants, revisions, and APIs.

This is why an employee guide can link to seren-agent endpoints or a managed agent grant. The endpoint name reflects the platform contract. The surrounding workflow still belongs to Seren Employees.

Work cycle

Define, connect, run, review, improve

  1. 01

    Define the job

    Give the employee a focused role, durable instructions, and a clear definition of successful work.

  2. 02

    Connect what it needs

    Add skills, knowledge, accounts, files, or data services with access limited to the job.

  3. 03

    Run the work

    Start work from the web, desktop, an MCP client, the CLI, an SDK, or an application using the API.

  4. 04

    Review important actions

    Let read-only investigation continue while protected changes wait for an explicit approval.

  5. 05

    Improve the system

    Review activity and outcomes, then refine instructions, skills, access, or review policy before automating more work.

Product layer

Give employees controlled capabilities

Passwords

Provides controlled access to credentials without placing secret values in prompts or ordinary configuration.

Explore Passwords

Skills

Packages repeatable instructions and supporting files for work your organization performs regularly.

Explore Skills

Memory

Captures policy-permitted agent context into private memory, injects reviewed facts, and provides governed organizational knowledge across related work.

Explore Memory

Storage

Provides scoped buckets and durable files for inputs, outputs, and employee workspaces.

Explore Storage

Database

Provides branchable Postgres plus automatic organization- and user-scoped databases for skill working data.

Explore Database

Approvals

Pauses protected actions for review while allowing permitted preparation and investigation to continue.

Explore Approvals

Boundaries

Access follows the employee identity

Grant access to the employee that needs it, not to every employee in the organization. Prefer read-only access for research and analysis, add write access only when the job requires it, and use approval policy for changes that must remain under human review. Revoke a grant when the work no longer needs that capability.

Seren creates a limited identity for each cloud employee. Do not copy your personal Seren API key into employee instructions, configuration, or Passwords. Skills use approved services through the employee's managed identity, while outside account credentials remain in their selected connector or credential grant.

Grant a credential

Entry points

Use the interface that fits the work

Use the Employees web app or Seren Desktop for conversational work, hosted MCP to bring Seren into an assistant, the CLI for terminal and automation workflows, and the SDK or API when Seren is part of an application.