Files
zed/docs/src/roles.md
Mohamad Khani b72a46db68
Some checks failed
Update All Top Ranking Issues / update_top_ranking_issues (push) Has been cancelled
Triage Project Sync (#84) / Sync triage project (push) Has been cancelled
release_nightly / notify_on_failure (push) Has been cancelled
release_nightly / check_style (push) Has been cancelled
release_nightly / run_tests_windows (push) Has been cancelled
release_nightly / clippy_windows (push) Has been cancelled
release_nightly / bundle_linux_aarch64 (push) Has been cancelled
release_nightly / bundle_linux_x86_64 (push) Has been cancelled
release_nightly / bundle_mac_aarch64 (push) Has been cancelled
release_nightly / bundle_mac_x86_64 (push) Has been cancelled
release_nightly / bundle_windows_aarch64 (push) Has been cancelled
release_nightly / bundle_windows_x86_64 (push) Has been cancelled
release_nightly / build_nix_linux_x86_64 (push) Has been cancelled
release_nightly / build_nix_mac_aarch64 (push) Has been cancelled
release_nightly / update_nightly_tag (push) Has been cancelled
Hotfix Review Monitor / check-hotfix-reviews (push) Has been cancelled
Stale PR Review Reminder / check-stale-prs (push) Has been cancelled
Update Weekly Top Ranking Issues / update_top_ranking_issues (push) Has been cancelled
Bump collab-staging Tag / update-collab-staging-tag (push) Has been cancelled
compliance_check / scheduled_compliance_check (push) Has been cancelled
logiguard fork: GPUI xdg-activation keyboard-focus serial fix
Single-commit orphan branch: full zed-industries/zed @ 8c74db0 source tree
with a 3-file patch applied (no upstream history).

Patch (crates/gpui_linux/src/linux/wayland/):
  - serial.rs: add SerialKind::KeyboardEnter
  - client.rs: store wl_keyboard.enter serial; add latest_serial_of()
  - window.rs: activate() uses keyboard-enter serial (Mutter focus gate)

Mutter honors window activation only when the token carries the keyboard-
focus serial from wl_keyboard.enter; GPUI used a stale mouse-press serial.
See docs/tray-window-focus-wayland.md in logiguard.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 02:22:17 +03:30

2.3 KiB

title, description
title description
Roles - Zed Understand Zed's organization roles and what each role can access, manage, and configure.

Roles

Every member of a Zed organization is assigned a role that determines what they can access and configure.

Role Types

Every member of an organization is assigned one of three roles:

Role Description
Owner Full control, including billing and ownership transfer
Admin Full control, except billing
Member Standard access, no privileged actions

Owner

An owner has full control over the organization, including:

  • Invite and remove members
  • Assign and change member roles
  • Manage billing, payment methods, and invoices
  • Configure data-sharing policies
  • Disable Zed's collaborative features
  • Control whether members can use Zed-hosted models and Zed's edit predictions
  • Transfer ownership to another member

Admin

Admins have the same capabilities as the Owner, except they cannot:

  • Access or modify billing settings
  • Transfer organization ownership

This role is suited for team leads or managers who handle day-to-day member access without needing visibility into payment details.

Member

Members have standard access to Zed. They cannot access billing or organization settings.

Managing User Roles

Owners and Admins can manage organization members from the Zed dashboard within the Members page.

Inviting Members

  1. On the Members page, select + Invite Member.
  2. Enter the member's company email address and choose a role.
  3. The invitee receives an email with instructions to join. After accepting, they authenticate via GitHub.

Changing a Member's Role

  1. On the Members page, find the member. You can filter by role or search by name.
  2. Open the three-dot menu and select a new role.

Removing a Member

  1. On the Members page, find the member.
  2. Select Remove and confirm.

Removing a member removes their access to organization settings and any organization-managed features. They can continue using Zed on their own.