Configure organization collaboration

Individual by default

Keep normal employee work personal

Employee work remains individual unless a person selects organization collaboration for that run. Membership, an assignment, or a connected channel does not change this default.

Seren stops an organization request when an authority check fails. It never continues the request as individual work.

Before you start

Use a current managed employee

The employee must use the managed Seren Agent runtime. Its active deployment must have an immutable deployment revision and a stable agent identity.

Collaboration management requires a signed-in owner or administrator. API keys cannot change this authority. Mutation requests also require the organization security scope from the current sign-in session.

Step 1

Assign the employee

Create an assignment before you enable the organization policy. The assignment selects the capabilities that this employee can use.

The available capabilities cover organization knowledge, credentials, skills, and artifact writes. Task labels can narrow the allowed work. A task label classifies a run, but it never grants a capability.

PUT /organizations/{organization_id}/employee-collaboration/assignments/{deployment_id}

{
  "organization_knowledge_read": true,
  "organization_credential_use": false,
  "organization_skill_use": true,
  "organization_artifact_write": false,
  "allowed_task_labels": ["research.review"]
}

If no assignment exists, omit expected_assignment_generation . For every update, include the current generation.

Step 2

Enable the organization policy

Read the current policy after the assignment exists. Then enable only the capabilities that the organization permits.

GET /organizations/{organization_id}/employee-collaboration-policy

PUT /organizations/{organization_id}/employee-collaboration-policy

{
  "expected_policy_revision": "{revision_from_get}",
  "enabled": true,
  "organization_knowledge_read": true,
  "organization_credential_use": false,
  "organization_skill_use": true,
  "organization_artifact_write": false
}

If the policy read returns baseline, use that revision. A stale revision returns a conflict instead of replacing a newer policy.

The policy sets the organization maximum. The assignment can only narrow that maximum. Enabling the policy alone grants nothing.

Step 3

Select organization work for one run

Select Organization in the employee composer. Then select an allowed task label and an organization-visible Seren Memory domain when the run needs shared knowledge.

The CLI and MCP tool use the same explicit selection. If the run does not need shared knowledge, omit the knowledge selection.

seren agent cloud run start   --deployment-id <deployment-id>   --organization   --knowledge-selection-id <memory-domain-id>   --task-label research.review   --message "Review the current research brief."

In MCP, call run_cloud_agent with organization: true. The tool also accepts the knowledge selection and task label.

Signed work context

Understand what the signed context binds

Seren Core creates a short-lived, signed OrganizationWorkContext for an authorized run. Clients do not create, edit, or submit this token.

The context binds the organization, user, employee identity, deployment, deployment revision, policy revision, and assignment generation. It also binds the run origin, knowledge selection, capture target, task label, and output audience.

The context describes the requested authority boundary. It does not grant access by itself. Each Seren service checks its current resource grants before every protected operation.

Knowledge boundary

Use organization-visible knowledge

Organization-targeted employee runs currently read only organization-visible Memory domains. Seren rejects a restricted domain for an organization audience.

Seren Memory resolves the opaque knowledge selection and checks its current grants. Revoking domain access blocks the next protected read.

Separate read and capture

Choose each data destination

Reading organization knowledge does not write the run into that domain. It also does not copy the run into personal memory.

The signed contract keeps capture target, output audience, run origin, and knowledge selection separate. The current direct-run API accepts only no capture and the organization audience.

Revocation

Stop authority at the next operation

Disable the organization policy to stop all new organization runs. Revoke one assignment to stop that employee.

DELETE /organizations/{organization_id}/employee-collaboration/assignments/{deployment_id}?expected_assignment_generation={generation}

POST /organizations/{organization_id}/employee-collaboration/assignments/{deployment_id}/reactivate

{
  "expected_assignment_generation": 4,
  "organization_knowledge_read": true,
  "organization_credential_use": false,
  "organization_skill_use": true,
  "organization_artifact_write": false,
  "allowed_task_labels": ["research.review"]
}

Protected services check current authority again on each call. Revocation blocks the next call, even when the run already has a signed context. Seren does not fall back to individual work.

Audit

Review tamper-evident authority events

Seren records policy changes, assignment changes, authority use, and denied authority in the organization audit chain.

The action names include organization_employee_collaboration_authority_exercised and organization_employee_collaboration_authority_denied. Use the Seren Cloud audit API to filter entries by action.

Independent grants

Grant each capability separately

Organization knowledge does not grant access to Passwords, Storage, Skills, or connectors. Each service checks its own current grant.

The organization policy and employee assignment must also allow the requested capability. Both checks must pass before a protected call.

Direct connector tools, built-in runtime memory, and the app_server adapter do not support organization runs. Review the current runtime limits before you design the employee workflow.

Connected channels

Do not treat a channel as authority

A connected channel starts normal individual work by default. A channel connection does not grant organization authority or define an output audience.

Channel-scoped organization collaboration is not enabled yet. Core rejects a channel origin instead of creating a signed context or falling back to individual work. A future channel path must require a current organization-managed binding.