Skip to content

Team mode M3: Host Roles, permission catalog, member and device management #4142

Closed

Description

@DoodleBears

Parent: hub #4138 (spec #4137, ADR-0336). Blocked by: #4140.

Behavior

  • A fixed Host Permission catalog and built-in Admin and Member roles.
    • Member defaults: private Bots, Channels, Human DMs and configured models.
    • Admin: everything except viewing private content and transferring ownership.
  • Custom roles with union semantics.
  • Owner transfer.
  • Admin UI for members, roles and each member's devices.
  • CLI: roles, members, devices --member.

Acceptance

  • Removing a permission takes effect on the member's next call.
  • A Member is refused each Admin action through the Client and the CLI with --as.
  • The Owner cannot be deleted.

Activity

  1. DoodleBears commented on Nov 13, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: Claude Code (orchestrator, UI/UX) + Codex CLI (logic)
    • Task: claude/local/74a5ee4a-f6fe-4aab-870f-5e465b0b8474 (not a DSH Session); Codex thread added once started
    • Issue scope: M3 per the contract below
    • Branch: claude/4142-host-roles (stacked on claude/4140-team-sign-in, PR Team mode M1: members sign in over HTTPS and talk in public channels #4163; Codex sub-branch codex/4142-logic)
    • Started: 2026-11-13 23:06 UTC
    • State: active

    M3 wire contract (agreed before parallel work; Claude = UI, Codex = logic)

    Stacked on M1 (#4163). Password reset, suspension and offboarding stay in M9 (#4147).

    Host Permission catalog (fixed, code-defined ids; union across a member's roles)
    members.manage (create members, assign roles, see and revoke members' devices) · roles.manage · team.settings (Team mode switch, plain-HTTP exception, public flag on any Channel) · channels.create · channels.manageAll · dm.humans · bots.create · bots.manageAll · models.use · im.bind · workspaces.manageShared · approvals.opaqueTools · usage.view · audit.view · privateContent.view.
    The Owner holds every permission implicitly and is not a role. Permissions that later slices enforce (bots.*, dm.humans, models.use, im.bind, workspaces.*, approvals.*, usage.view, audit.view, privateContent.view) are stored and shown in M3; their enforcement lands in the slice that owns them.

    Built-in roles (not deletable, permissions editable except as noted): admin = every permission except privateContent.view (never grantable through Admin); member = channels.create, dm.humans, bots.create, models.use. New members get member. Existing M1 members migrate to member.

    Bridge methods (refusals as BridgeCallError codes; permission-required carries details.permission)

    Method Needs Result / refusals
    teamMode (extended) anyone viewer gains permissions: string[], roleIds: string[], owner: boolean
    permissionCatalog anyone signed in [{ id, group: 'members'|'channels'|'bots'|'compute'|'oversight' }] (ids only; the UI owns labels)
    roles roles.manage or members.manage [{ roleId, name, builtin: 'admin'|'member'|null, permissions: string[], memberCount }]
    roleCreate { name, permissions } roles.manage { role } · role-name-invalid, role-name-taken, permission-unknown
    roleUpdate { roleId, name?, permissions? } roles.manage { role } · role-not-found, role-name-taken, permission-unknown, permission-not-grantable (privateContent.view on admin)
    roleDelete { roleId } roles.manage role-builtin, role-not-found; members keep their other roles; a member left with no role gets member
    members (extended) members.manage rows gain roleIds: string[], deviceCount
    memberCreate { username, displayName, roleIds? } members.manage as M1; roleIds default ['member']
    memberRolesSet { humanId, roleIds } members.manage member-not-found, owner-protected (the Owner has no roles), role-not-found; only the Owner may grant admin (permission-required)
    memberDevices { humanId } members.manage or self [{ grantId, label, kind: 'browser'|'paired-device', createdAt, lastSeenAt, current }]
    memberDeviceRevoke { humanId, grantId } members.manage or self device-not-found; revoking disposes that grant's Peer at once
    ownerTransfer { humanId, password } Owner only credentials-invalid (Owner's password), member-not-found, member-suspended; the old Owner becomes a member with admin
    Removing a permission takes effect on the member's next call (policy re-evaluates; remoteAccess.invalidate). Members still cannot call DSH-native methods.

    CLI: roles list|create|update|delete, members roles <username> --set <role,...>, devices --member <username> [--revoke <grantId>], team-mode transfer-owner <username> --password-stdin --confirm; --as works for all.

    Client (Claude): Team › Members rows open a member sheet (roles, devices with revoke); Team › Roles list with create/edit dialog (permission checkboxes grouped by group) and delete confirm; Owner transfer as a danger action with password; members without members.manage/roles.manage see no admin UI; en + zh.

  2. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Nov 13, 2026
  3. DoodleBears commented on Nov 13, 2026

    @DoodleBears
    ContributorAuthor

    Codex logic task for this claim: codex/local/01a1d729-cdcb-7df0-86a4-9b4bfe3a4040 on codex/4142-logic (gpt-6.1-sol, high).

  4. DoodleBears commented on Nov 14, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

  5. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions