Manage employees in your organization

Employee model

Define the role and its authority

An organization employee has a managed deployment, an immutable revision, and a stable agent identity. The identity receives only the resources that the employee needs.

Instructions define the job. Skills define reusable procedures. Resource grants, capability policy, and approvals control the actions that the employee can perform.

Opt-in collaboration

Select organization work for each run

Employee work is individual by default. Membership, an employee assignment, or a connected channel does not change this default.

An organization run requires an explicit organization selection. It can also select shared knowledge and an organization-defined task label. Organization runs currently accept direct invocation only, write no captured knowledge, and return to the organization audience.

Seren stops the organization request if an authority check fails. It does not continue the request as individual work.

Authority

Require all three authorization layers

The organization policy defines the maximum collaboration authority. The employee assignment can only narrow that authority.

Each protected service also checks its current resource grant. A capability is available only when all three control layers permit it.

Collaboration capabilities cover organization knowledge, credentials, skills, and artifact writes. Task labels can restrict the permitted work, but a task label never grants a capability.

Work context

Bind the selected work boundary

Seren Core creates a short-lived, signed work context for each authorized organization run. Clients do not create or edit this context.

The context binds the user, employee, deployment revision, policy, assignment, origin, task label, knowledge selection, capture target, and output audience.

The context records the requested boundary. It is not a resource grant. Each service checks current authority before a protected operation.

Data ownership

Keep organization data inside its boundary

Organization conversations, messages, tool records, connector mappings, and encrypted content belong to the organization. Seren keeps this product data in isolated organization service storage.

Shared knowledge, capture, and output are separate selections. Reading organization knowledge does not copy a run into shared or personal memory.

Use Memory for recalled knowledge. Use Storage for files. Use an organization-scoped skill database for shared transactional records.

Channels

Treat a channel as an entry point

Slack and other connected channels can start ordinary employee work. A channel connection does not grant organization authority or define an output audience.

Channel-scoped organization collaboration is not enabled yet. Core currently rejects a channel origin instead of treating it as direct or individual work. A future channel path must require a current managed binding and include its generation in the work boundary.

Current limits

Understand current runtime limits

Direct connector tools are not available during an organization run. The current connector path cannot revalidate the work context or bind an approval to each action. Do not design organization work that depends on direct connector actions.

Organization collaboration currently starts through a direct run. A connected Slack or other channel can start ordinary employee work, but it cannot select organization collaboration yet.

Built-in semantic and graph memory tools are also unavailable during an organization run. These tools do not support an organization-scoped runtime namespace. Use Seren Memory for organization knowledge.

The app_server runtime adapter does not accept organization work. Configure organization collaboration on the default managed runtime. A deployment that combines the two stops with a configuration error instead of running with reduced authority.

Lifecycle

Revoke, review, and improve

An administrator can disable the organization policy or revoke one employee assignment. Protected services apply revocation at the next operation.

A work context is bound to the deployment revision that was active when Seren issued it. Publishing a new revision ends the authority of contexts issued against the previous one. As a result, organization work in progress stops at its next protected operation. Treat a revision change as a deployment change.

The organization audit chain records policy changes, assignment changes, authorized operations, and denied operations. Immutable deployment revisions support review and rollback.