docs: update roles, access settings, and audit docs for multi-owner support

- Update roles-and-permissions to document multiple owners and
  promote/demote workflows
- Update access-settings to use plural owner references
- Add new audit events: org.member_promoted_to_owner,
  org.owner_demoted_to_member

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: brendan-kellam

docs/docs/configuration/audit-logs.mdx

@@ -134,6 +134,8 @@ curl --request GET '$SOURCEBOT_URL/api/ee/audit' \
 | `user.signed_out`                     | `user` | `user` |
 | `org.ownership_transfer_failed`       | `user` | `org` |
 | `org.ownership_transferred`           | `user` | `org` |
+| `org.member_promoted_to_owner`        | `user` | `user` |
+| `org.owner_demoted_to_member`         | `user` | `user` |
 
 
 ## Response schema

docs/docs/configuration/auth/access-settings.mdx

@@ -17,20 +17,20 @@ When accessing Sourcebot anonymously, a user's permissions are limited to that o
 
 # Member Approval 
 
-By default, Sourcebot requires new members to be approved by the owner of the deployment. This section explains how approvals work and how
+By default, Sourcebot requires new members to be approved by an owner of the deployment. This section explains how approvals work and how
 to configure this behavior.
 
 ### Configuration
-Member approval can be configured by the owner of the deployment by navigating to **Settings -> Access**, or by setting the `REQUIRE_APPROVAL_NEW_MEMBERS` environment variable. When the environment variable is set, the UI toggle is disabled and the setting is controlled by the environment variable.
+Member approval can be configured by an owner of the deployment by navigating to **Settings -> Access**, or by setting the `REQUIRE_APPROVAL_NEW_MEMBERS` environment variable. When the environment variable is set, the UI toggle is disabled and the setting is controlled by the environment variable.
 
 ![Member Approval Toggle](/images/member_approval_toggle.png)
 
 ### Managing Requests
 
 If member approval is enabled, new members will be asked to submit a join request after signing up. They will not have access to the Sourcebot deployment
-until this request is approved by the owner.
+until this request is approved by an owner.
 
-The owner can see and manage all pending join requests by navigating to **Settings -> Members**.
+Owners can see and manage all pending join requests by navigating to **Settings -> Members**.
 
 ## Invite link
 

docs/docs/configuration/auth/roles-and-permissions.mdx

@@ -9,6 +9,26 @@ Each member has a role which defines their permissions within an organization:
 
 | Role | Permission |
 | :--- | :--------- |
-| `Owner` | Each organization has a single `Owner`. This user has full access rights, including: connection management, organization management, and inviting new members. |
+| `Owner` | An organization can have one or more `Owner`s. Owners have full access rights, including: connection management, organization management, and inviting new members. |
 | `Member` | Read-only access to the organization. A `Member` can search across the repos indexed by an organization's connections, as well as view the organizations configuration and member list. However, they cannot modify this configuration or invite new members. |
-| `Guest` | When accessing Sourcebot [anonymously](/docs/configuration/auth/access-settings#anonymous-access), a user has the `Guest` role. `Guest`'s can search across repos indexed by an organization's connections, but cannot view any information regarding the organizations configuration or members. |
+| `Guest` | When accessing Sourcebot [anonymously](/docs/configuration/auth/access-settings#anonymous-access), a user has the `Guest` role. `Guest`'s can search across repos indexed by an organization's connections, but cannot view any information regarding the organizations configuration or members. |
+
+## Managing owners
+
+import LicenseKeyRequired from '/snippets/license-key-required.mdx'
+
+<LicenseKeyRequired />
+
+Organizations support multiple owners, allowing you to share administrative responsibilities across your team. Owners can promote members to owner and demote other owners back to member from **Settings -> Members**.
+
+### Promoting a member to owner
+
+To promote a member, click the action menu (three dots) next to their name in the members list and select **Promote to owner**. The member will immediately gain full administrative access.
+
+### Demoting an owner to member
+
+To demote an owner, click the action menu next to their name and select **Demote to member**. Owners can also demote themselves to step down from the role. The last remaining owner of an organization cannot be demoted — at least one owner must exist at all times.
+
+### Leaving an organization as an owner
+
+An owner can leave the organization as long as at least one other owner exists. If you are the last owner, you must promote another member to owner before leaving.