Skip to content
AFK / Docs

Search page titles and summaries. Shortcut: Ctrl / ⌘ K.

Team operations

AFK's team layer is organized around organisations, shared session visibility, assignments, handoffs, mentions, and shared operational settings. These features let teams supervise agent work without moving execution out of the daemon.

Organisations and context

AFK can run in personal context or organisation context. When you switch to an org in the browser, user-scoped resources such as sessions, preferences, daemons, automations, plugins, skills, agents, rules, MCP config, hooks, and billing are read and written for that org.

  • Org-owned sessions store owner_user_id as the org andspawned_by as the real member who launched the work.
  • Daemons registered to an org are available to members according to the org access checks enforced by the Hub.
  • Org preferences provide shared LLM connections, API keys, webhooks, plugins, and other team configuration.

Roles

Organisation members can be admin, manager, ormember. Admin-only configuration surfaces such as LLM connections, API keys, and webhooks are hidden for non-admin users and blocked server-side.

RoleTypical access
adminManage org settings, members, shared credentials, webhooks, and billing surfaces.
managerSee Org-visible sessions across the organisation and manage members without editing admin-only configuration. Restricted sessions require an explicit relationship.
memberUse the org workspace and read Org-visible sessions. Restricted sessions require ownership, assignment, or explicit sharing.

Where org settings live

Organisation settings are reachable from both workspaces. In a personal workspace they are under Account → Orgs, where each org card expands to its members, reporting teams, policies, and lifecycle actions. While an organisation is the active workspace they are under Account → Org, which shows the org profile, members, reporting teams, and the shared policies below. Creating an organisation and switching between workspaces stay in the personal workspace.

Shared policy covers whether members may use personal daemons and model connections for org sessions and org automations, and whether agent tools may access all organisation sessions. Owners and admins can change these; other roles do not see the controls. Members can leave an organisation from either location, and an owner deletes the organisation from the personal workspace.

Member machines

When an organisation allows personal daemons, a member can run that organisation's sessions and automations on their own connected machines, alongside the organisation's shared daemons. A colleague's personal machine is never offered to you: it does not appear in your machine list, cannot be selected for a session, and is not used by automations. Seeing other people's laptops is not something an organisation setting can turn on.

Availability is decided by the member who owns the machine, from Account → Machines in their personal workspace: each machine summarises the contexts it can appear in, starting with the member's own personal workspace, and unticking one in the dropdown withdraws the machine from that context only. Organisations joined later are included automatically, and withdrawing a machine takes effect immediately. Organisation-owned shared daemons are separate and remain visible to every member.

Withdrawing a machine changes where work may run, not which machine you can configure. Its plugins, MCP servers, hooks, guidelines, skills, agents, and LSP overrides stay reachable from the matching settings tabs in your personal workspace, so a machine reserved for organisation work can still be maintained from the same place as the others.

The same settings tabs keep listing a machine while its daemon is not running, marked offline. Nothing on that machine can be read or changed until the daemon starts again, but it does not disappear from the list in the meantime — start the daemon and the same machine, with the same configuration, is back.

A machine you no longer recognise — for example one left behind after a reinstall or a throwaway container — can be removed with Forget. It has to be offline first: a running daemon checks back in and would simply reappear. Forgetting a machine only removes it from this list; the sessions it ran stay in your history.

Invites and inbox

The Inbox button in the sidebar opens a personal notification panel. It is intentionally personal: it does not switch with org context, so a user can accept invites and handoffs no matter which workspace is active. Opening the panel marks unread items as read; acting on an item dismisses it.

Inbox itemWhat it meansActions
Org inviteAn admin or manager invited you to join an organisation with a role.Accept joins the org and removes the item. Decline rejects the invite and removes the item.
Session handoffA session was assigned to you, often with a note from the previous owner.Open jumps to the session. Reject clears the assignment and dismisses the item.
UnassignedYou were removed from a session assignment.Dismiss acknowledges the notification.

Org admins and managers invite members from Account → Members. Invitees receive an org invite item with the org name, role, inviter, and accept/decline actions.

Reporting teams

Reporting teams are an optional way to organise usage and outcome metrics inside one organisation. Owners and admins can create a nested team hierarchy from Account → Orgs in a personal workspace, or from Account → Org while that organisation is the active workspace, then assign each active member to one team and leave anyone else Unallocated. Managers can view the hierarchy in the org workspace but cannot change it.

New work keeps its reporting attribution: top-level sessions use the initiating member’s team, child sessions inherit their parent’s team, and automations may be assigned a reporting team. Moving a member, reassigning a session, or reorganising teams does not rewrite earlier work.

In Dashboard → Metrics, selecting a team includes its current descendant teams. Archived teams remain available in reports so historical activity can still be understood. The hierarchy is for reporting only: it never changes session visibility, action permissions, billing, shared settings, or automation access.

The dashboard is the team's operations surface for live and historical agent work. New sessions created in an organisation default to Org visible, so active members can discover and read them. Restricted sessions appear only to the owner/spawner, assignee, explicitly shared participants, and org owners or admins. Managers do not receive a Restricted-session read override; they need one of those explicit session relationships.

Personal sessions remain private. Older org sessions that predate these visibility choices show Legacy access and keep their previous access rules until an authorised session manager chooses Org visible or Restricted.

Shared sessions

Organisation sessions can be shared with additional teammates. Personal sessions remain private and do not expose team-sharing controls. Sharing is intended for collaborative agent operations: letting another person observe work, answer when appropriate, or take context from a durable transcript without copying it into a separate chat tool.

VisibilityWho can read the session
Org visibleEvery active member of the organisation.
RestrictedThe owner/spawner, assignee, explicitly shared participants, and org owners or admins. Managers need an explicit relationship to the session.
Legacy accessOlder sessions keep the access rules that applied before visibility choices were introduced.

Visibility controls who can discover and read a session; it does not by itself grant permission to send messages, approve tool calls, assign or share the session, change settings, or manage its lifecycle. AFK checks those actions separately from read access.

Participant roleWhat the participant can do
viewerOpen the shared session, read transcript/history/context, and reconnect later, but not send prompts, approve tools, edit pending messages, or change session settings.
contributorDo everything a viewer can do, plus respond to or steer an unassigned shared session. If the session is assigned, the assignment lock still applies.

The owner/spawner and org owners/admins can manage participants. Read access does not bypass the response lock on an assigned session; only the owner/spawner or current assignee can respond.

Session side controls such as rename, clear history, compact, model or mode changes, context-window changes, schedule cancellation, reload, and stop/close are permission guarded for the owner/spawner. Contributors are for collaborative steering, not administrative mutation of the session.

Participant add, role-change, and remove events are written into the session history so collaborators can understand how access changed over time. When an unassigned shared session is waiting for user input or an approval, contributor participants receive waiting-work inbox items along with the owner/spawner; viewers do not. Assigned sessions route waiting work to the assignee.

Assignments and handoff

Sessions can be assigned or unassigned across org members from session list actions and team workflows. Assignment metadata includes the assignee and optional notes, appears in session lists, and creates inbox notifications for handoffs. Use assignments when a running agent needs another teammate's attention or when ownership of follow-up work should move to someone else.

  1. Assign the session to a member and include a note when context matters.
  2. The assignee receives a personal Inbox handoff item.
  3. Opening the item selects the session and dismisses the notification.
  4. Rejecting the handoff clears the assignment so the team can re-route it.

Session mentions

The chat composer supports mentioning live sessions and child agents. Use a bare mention such as @reviewer or a braced mention such as @{Frontend Review} to route a message to another session. AFK resolves clear targets, asks for clarification when ambiguous, fans out multi-target dispatches, and records dispatch events in history.

Mentions use the same send_message delivery path as agent P2P messaging. Cross-account relay is rejected; same-account and same-org delivery is routed through the owning daemon via the Hub when needed.

Current and future governance

Built today: org roles, Org-visible, Restricted, and Legacy session visibility, shared dashboards, shared-session participants, member filters, assignments, inbox invites and handoff notifications, permission modes, plan review, hooks, webhooks, and durable session memory. Future governance work is policy-driven: richer audit views, SSO/SCIM, high-risk workflow review, escalation for stale waiting work, and policy simulation.