How Seren works

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. The underlying platform represents parts of that employee as agents, deployments, runs, identities, grants, and revisions. Product guidance uses employee when it describes the managed experience and agent when it refers to those platform resources or APIs.

This is why an employee guide may link to seren-agent endpoints or an 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

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 should remain under human review. Revoke a grant when the work no longer needs that capability.