From 32701234b210f9a9bcc8b20c8f84ea313173117e Mon Sep 17 00:00:00 2001 From: openhands Date: Tue, 28 Apr 2026 00:22:22 +0000 Subject: [PATCH 1/9] Add Organizations documentation for OpenHands Cloud Add documentation for the Organizations feature, which is a commercial feature available with OpenHands Cloud subscription or OpenHands Enterprise. New documentation pages: - organizations/overview.mdx - Feature overview and key capabilities - organizations/managing-members.mdx - How to invite and manage users - organizations/roles-permissions.mdx - Permissions table and role descriptions - organizations/settings.mdx - LLM config, credits, and Git org claiming Updated docs.json to add Organizations section to the Cloud tab. Co-authored-by: openhands --- docs.json | 10 +++ .../cloud/organizations/managing-members.mdx | 55 ++++++++++++ .../usage/cloud/organizations/overview.mdx | 43 ++++++++++ .../cloud/organizations/roles-permissions.mdx | 81 +++++++++++++++++ .../usage/cloud/organizations/settings.mdx | 86 +++++++++++++++++++ 5 files changed, 275 insertions(+) create mode 100644 openhands/usage/cloud/organizations/managing-members.mdx create mode 100644 openhands/usage/cloud/organizations/overview.mdx create mode 100644 openhands/usage/cloud/organizations/roles-permissions.mdx create mode 100644 openhands/usage/cloud/organizations/settings.mdx diff --git a/docs.json b/docs.json index 4337398f6..fdf50dd61 100644 --- a/docs.json +++ b/docs.json @@ -385,6 +385,16 @@ "openhands/usage/cloud/cloud-ui" ] }, + { + "group": "Organizations", + "icon": "building", + "pages": [ + "openhands/usage/cloud/organizations/overview", + "openhands/usage/cloud/organizations/managing-members", + "openhands/usage/cloud/organizations/roles-permissions", + "openhands/usage/cloud/organizations/settings" + ] + }, { "group": "Settings", "pages": [ diff --git a/openhands/usage/cloud/organizations/managing-members.mdx b/openhands/usage/cloud/organizations/managing-members.mdx new file mode 100644 index 000000000..2a1c4b76e --- /dev/null +++ b/openhands/usage/cloud/organizations/managing-members.mdx @@ -0,0 +1,55 @@ +--- +title: Managing Members +description: How to invite users and manage team members in your organization. +--- + +## Inviting Users + +To add a new member to your organization: + +1. Navigate to your organization's settings page. +2. Select the `Members` tab. +3. Click `Invite Member`. +4. Enter the email address of the user you want to invite. +5. Click `Send Invite`. + +The invited user will receive an email with instructions to accept the invitation and join your organization. +Once they accept, they will be added as a **Member** by default. + + + Invitations expire after 7 days. If the invitation expires, you'll need to send a new one. + + +## Changing User Roles + +After a user has joined your organization, you can modify their role: + +1. Navigate to your organization's settings page. +2. Select the `Members` tab. +3. Find the user whose role you want to change. +4. Click the role dropdown next to their name. +5. Select the new role: `Owner`, `Admin`, or `Member`. +6. Confirm the change. + + + Changing a user's role takes effect immediately. Be careful when demoting users, as they will lose access + to features associated with their previous role. + + +## Removing Members + +To remove a member from your organization: + +1. Navigate to your organization's settings page. +2. Select the `Members` tab. +3. Find the user you want to remove. +4. Click the `Remove` button next to their name. +5. Confirm the removal. + +Removed members will lose access to the organization's shared resources immediately, but their private +conversations will remain intact. + +## Next Steps + +- [Roles and Permissions](/openhands/usage/cloud/organizations/roles-permissions) - Understand what each role can do. +- [Organization Settings](/openhands/usage/cloud/organizations/settings) - Configure your organization's resources. diff --git a/openhands/usage/cloud/organizations/overview.mdx b/openhands/usage/cloud/organizations/overview.mdx new file mode 100644 index 000000000..60a93635b --- /dev/null +++ b/openhands/usage/cloud/organizations/overview.mdx @@ -0,0 +1,43 @@ +--- +title: Organizations Overview +description: Manage teams and collaborate with shared resources in OpenHands Cloud. +--- + +## What are Organizations? + +Organizations allow multiple users to collaborate within a shared workspace in OpenHands Cloud. With +Organizations, teams can share a pool of credits, use consistent LLM configurations, and streamline access +to repositories. + + + Organizations is a commercial feature available with an OpenHands Cloud subscription or OpenHands Enterprise. + + +## Key Features + +Organizations provide the following capabilities: + +- **Multiple Users** - Add team members to a common organization for centralized management. +- **Shared Credits** - Pool OpenHands Cloud credits across all organization members. +- **Default LLM Configuration** - Define the default model provider and LLM that all members can use. +- **Git Organization Claiming** - Claim specific Git organizations to route OpenHands resolver requests to your organization. + +## Conversation Visibility + +By default, conversations remain **private to individual members** of an organization. Each user's conversations +are only visible to them, even when working within the same organization. + +## Getting Started + +To start using Organizations: + +1. Subscribe to an OpenHands Cloud plan or OpenHands Enterprise. +2. Create a new organization from the OpenHands Cloud dashboard. +3. [Invite team members](/openhands/usage/cloud/organizations/managing-members) to join your organization. +4. Configure your organization's [LLM settings](/openhands/usage/cloud/organizations/settings) and shared resources. + +## Next Steps + +- [Managing Members](/openhands/usage/cloud/organizations/managing-members) - Learn how to invite users and manage roles. +- [Organization Settings](/openhands/usage/cloud/organizations/settings) - Configure LLM providers, credits, and Git organization claims. +- [Roles and Permissions](/openhands/usage/cloud/organizations/roles-permissions) - Understand the different permission levels. diff --git a/openhands/usage/cloud/organizations/roles-permissions.mdx b/openhands/usage/cloud/organizations/roles-permissions.mdx new file mode 100644 index 000000000..2d98e1928 --- /dev/null +++ b/openhands/usage/cloud/organizations/roles-permissions.mdx @@ -0,0 +1,81 @@ +--- +title: Roles and Permissions +description: Understanding the different permission levels in OpenHands Organizations. +--- + +## Overview + +Organizations in OpenHands support three roles, each with different levels of access and capabilities: +**Member**, **Admin**, and **Owner**. This page describes what each role can do. + +## Permissions Table + +| Permission | Member | Admin | Owner | +|------------|:------:|:-----:|:-----:| +| Create conversations | ✓ | ✓ | ✓ | +| Manage private settings | ✓ | ✓ | ✓ | +| Invite users | | ✓ | ✓ | +| Change Member to Admin role | | ✓ | ✓ | +| Add credits | | ✓ | ✓ | +| Modify LLM settings | | ✓ | ✓ | +| Claim Git organizations | | | ✓ | +| Delete organization | | | ✓ | + +## Role Descriptions + +### Member + +Members are the default role for users joining an organization. Members can: + +- **Create conversations** - Start new conversations using the organization's shared credits. +- **Manage their own private settings** - Configure settings that are only visible to them, including: + - MCP servers + - Secrets + - API keys + - Git settings + - Slack integration + +Members cannot invite new users, modify organization-wide settings, or manage other users' roles. + +### Admin + +Admins have all the capabilities of Members, plus the ability to manage the organization's settings and users. Admins can: + +- Everything a Member can do. +- **Invite users** - Send invitations to new team members. +- **Change user roles** - Promote Members to Admin or demote Admins to Members. +- **Add credits** - Purchase and add credits to the organization's shared pool. +- **Modify LLM settings** - Configure the default LLM provider and model for the organization. + +Admins cannot delete the organization or claim Git organizations. + +### Owner + +Owners have full control over the organization. Owners can: + +- Everything an Admin can do. +- **Delete the organization** - Permanently remove the organization and all associated data. +- **Claim Git organizations** - Link specific Git organizations to route OpenHands resolver requests to this organization. + + + Every organization must have at least one Owner. If you need to transfer ownership, first promote another + user to Owner before changing your own role. + + +## Private Settings + +Regardless of role, all organization members have control over their own **private settings**. These settings +are personal to each user and are not visible to other organization members, including Admins and Owners. + +Private settings include: + +- **MCP Servers** - Configure Model Context Protocol servers. +- **Secrets** - Store sensitive values like API tokens and credentials. +- **API Keys** - Manage keys for programmatic access to OpenHands. +- **Git Settings** - Configure personal Git authentication and preferences. +- **Slack Integration** - Connect your personal Slack workspace. + +## Next Steps + +- [Managing Members](/openhands/usage/cloud/organizations/managing-members) - Learn how to invite and manage users. +- [Organization Settings](/openhands/usage/cloud/organizations/settings) - Configure organization-wide settings. diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx new file mode 100644 index 000000000..4cb2aae22 --- /dev/null +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -0,0 +1,86 @@ +--- +title: Organization Settings +description: Configure shared resources and settings for your OpenHands organization. +--- + +## Overview + +Organization settings allow Admins and Owners to configure shared resources that all members can use. This +includes LLM configurations, credits management, and Git organization claims. + +## LLM Configuration + + + Modifying LLM settings requires Admin or Owner permissions. + + +Organizations can define a default LLM provider and model that all members will use: + +1. Navigate to your organization's settings page. +2. Select the `LLM` tab. +3. Choose your preferred **LLM provider** from the available options. +4. Select the **model** you want to use as the default. +5. Click `Save Changes`. + +All organization members will use this LLM configuration for their conversations unless they have configured +personal overrides. + +## Managing Credits + + + Adding credits requires Admin or Owner permissions. + + +Organization credits are shared across all members. To add credits: + +1. Navigate to your organization's settings page. +2. Select the `Billing` tab. +3. Click `Add Credits`. +4. Choose the amount of credits to purchase. +5. Complete the payment process. + +Credits will be added to the organization's shared pool immediately and can be used by any member. + +### Monitoring Usage + +You can monitor credit usage from the `Billing` tab, which shows: + +- Current credit balance +- Credit usage over time +- Usage breakdown by member (for Admins and Owners) + +## Claiming Git Organizations + + + Claiming Git organizations requires Owner permissions. + + +Claiming a Git organization links it to your OpenHands organization, allowing OpenHands resolver requests +for repositories in that Git organization to be routed to your organization. + +To claim a Git organization: + +1. Navigate to your organization's settings page. +2. Select the `Git Organizations` tab. +3. Click `Claim Organization`. +4. Select the Git provider (GitHub, GitLab, or Bitbucket). +5. Enter the name of the Git organization you want to claim. +6. Complete the verification process. + + + You must have admin access to the Git organization to claim it. The verification process confirms your + authorization. + + +### Benefits of Claiming Git Organizations + +When a Git organization is claimed: + +- All resolver requests for repositories in that Git organization are automatically routed to your OpenHands organization. +- Organization members can work seamlessly with repositories in the claimed Git organization. +- Usage is tracked against your organization's credit pool. + +## Next Steps + +- [Managing Members](/openhands/usage/cloud/organizations/managing-members) - Invite users and manage roles. +- [Roles and Permissions](/openhands/usage/cloud/organizations/roles-permissions) - Understand permission levels. From ee55091220522c0f25e0ba2c82820be3d318e4f3 Mon Sep 17 00:00:00 2001 From: jpelletier1 <44589723+jpelletier1@users.noreply.github.com> Date: Mon, 27 Apr 2026 20:32:54 -0400 Subject: [PATCH 2/9] Updates --- .../cloud/organizations/managing-members.mdx | 14 +++++++------- openhands/usage/cloud/organizations/overview.mdx | 6 +++--- .../cloud/organizations/roles-permissions.mdx | 4 ++-- openhands/usage/cloud/organizations/settings.mdx | 16 ++++++++-------- 4 files changed, 20 insertions(+), 20 deletions(-) diff --git a/openhands/usage/cloud/organizations/managing-members.mdx b/openhands/usage/cloud/organizations/managing-members.mdx index 2a1c4b76e..3e738dbf6 100644 --- a/openhands/usage/cloud/organizations/managing-members.mdx +++ b/openhands/usage/cloud/organizations/managing-members.mdx @@ -7,11 +7,11 @@ description: How to invite users and manage team members in your organization. To add a new member to your organization: -1. Navigate to your organization's settings page. -2. Select the `Members` tab. -3. Click `Invite Member`. +1. Click the profile icon in the lower left +2. Select the `Org Members` tab. +3. Click `Invite Org Member`. 4. Enter the email address of the user you want to invite. -5. Click `Send Invite`. +5. Click `Add`. The invited user will receive an email with instructions to accept the invitation and join your organization. Once they accept, they will be added as a **Member** by default. @@ -22,10 +22,10 @@ Once they accept, they will be added as a **Member** by default. ## Changing User Roles -After a user has joined your organization, you can modify their role: +After a user has joined your organization, an Admin or Owner can modify their role: -1. Navigate to your organization's settings page. -2. Select the `Members` tab. +1. Click the profile icon in the lower left +2. Select the `Org Members` link 3. Find the user whose role you want to change. 4. Click the role dropdown next to their name. 5. Select the new role: `Owner`, `Admin`, or `Member`. diff --git a/openhands/usage/cloud/organizations/overview.mdx b/openhands/usage/cloud/organizations/overview.mdx index 60a93635b..924fd2132 100644 --- a/openhands/usage/cloud/organizations/overview.mdx +++ b/openhands/usage/cloud/organizations/overview.mdx @@ -1,11 +1,11 @@ --- title: Organizations Overview -description: Manage teams and collaborate with shared resources in OpenHands Cloud. +description: Manage teams and collaborate with shared resources in OpenHands Cloud or OpenHands Enterprise. --- ## What are Organizations? -Organizations allow multiple users to collaborate within a shared workspace in OpenHands Cloud. With +Organizations allow multiple users to collaborate within a shared workspace in OpenHands Cloud or OpenHands Enterprise. With Organizations, teams can share a pool of credits, use consistent LLM configurations, and streamline access to repositories. @@ -25,7 +25,7 @@ Organizations provide the following capabilities: ## Conversation Visibility By default, conversations remain **private to individual members** of an organization. Each user's conversations -are only visible to them, even when working within the same organization. +are only visible to them. ## Getting Started diff --git a/openhands/usage/cloud/organizations/roles-permissions.mdx b/openhands/usage/cloud/organizations/roles-permissions.mdx index 2d98e1928..e92b78678 100644 --- a/openhands/usage/cloud/organizations/roles-permissions.mdx +++ b/openhands/usage/cloud/organizations/roles-permissions.mdx @@ -32,10 +32,10 @@ Members are the default role for users joining an organization. Members can: - MCP servers - Secrets - API keys - - Git settings + - Git user settings - Slack integration -Members cannot invite new users, modify organization-wide settings, or manage other users' roles. +Members cannot invite new users, modify organization-wide settings (like LLM settings), or manage other users' roles. ### Admin diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx index 4cb2aae22..af6cb1e91 100644 --- a/openhands/usage/cloud/organizations/settings.mdx +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -33,9 +33,9 @@ personal overrides. Organization credits are shared across all members. To add credits: -1. Navigate to your organization's settings page. -2. Select the `Billing` tab. -3. Click `Add Credits`. +1. Click the profile icon in the lower left +2. Select the `Organization` link. +3. Click `Add`. 4. Choose the amount of credits to purchase. 5. Complete the payment process. @@ -43,7 +43,7 @@ Credits will be added to the organization's shared pool immediately and can be u ### Monitoring Usage -You can monitor credit usage from the `Billing` tab, which shows: +You can monitor credit usage from the `Organization` settings page, which shows: - Current credit balance - Credit usage over time @@ -58,11 +58,11 @@ You can monitor credit usage from the `Billing` tab, which shows: Claiming a Git organization links it to your OpenHands organization, allowing OpenHands resolver requests for repositories in that Git organization to be routed to your organization. -To claim a Git organization: +Owners have the ability to claim a Git organization: -1. Navigate to your organization's settings page. -2. Select the `Git Organizations` tab. -3. Click `Claim Organization`. +1. Click the profile icon in the lower left +2. Select the `Organization` link. +3. Under the `Git Conversation Routing` section, click `Claim` next to the Git organization to claim. 4. Select the Git provider (GitHub, GitLab, or Bitbucket). 5. Enter the name of the Git organization you want to claim. 6. Complete the verification process. From 9745f18c345b9f20084a19bcb5736f953ab25655 Mon Sep 17 00:00:00 2001 From: jpelletier1 <44589723+jpelletier1@users.noreply.github.com> Date: Mon, 27 Apr 2026 20:36:49 -0400 Subject: [PATCH 3/9] role perms --- openhands/usage/cloud/organizations/roles-permissions.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/openhands/usage/cloud/organizations/roles-permissions.mdx b/openhands/usage/cloud/organizations/roles-permissions.mdx index e92b78678..d4626fbef 100644 --- a/openhands/usage/cloud/organizations/roles-permissions.mdx +++ b/openhands/usage/cloud/organizations/roles-permissions.mdx @@ -15,9 +15,10 @@ Organizations in OpenHands support three roles, each with different levels of ac | Create conversations | ✓ | ✓ | ✓ | | Manage private settings | ✓ | ✓ | ✓ | | Invite users | | ✓ | ✓ | -| Change Member to Admin role | | ✓ | ✓ | +| Elevate users to Admin role | | ✓ | ✓ | | Add credits | | ✓ | ✓ | | Modify LLM settings | | ✓ | ✓ | +| Elevate users to Owner role| | | ✓ | | Claim Git organizations | | | ✓ | | Delete organization | | | ✓ | From 196594dfc2484d533bf51382f516b6624af703cf Mon Sep 17 00:00:00 2001 From: openhands Date: Tue, 28 Apr 2026 00:39:24 +0000 Subject: [PATCH 4/9] Move Organizations section to just above Automations in Cloud tab Co-authored-by: openhands --- docs.json | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs.json b/docs.json index fdf50dd61..4a01d609a 100644 --- a/docs.json +++ b/docs.json @@ -385,16 +385,6 @@ "openhands/usage/cloud/cloud-ui" ] }, - { - "group": "Organizations", - "icon": "building", - "pages": [ - "openhands/usage/cloud/organizations/overview", - "openhands/usage/cloud/organizations/managing-members", - "openhands/usage/cloud/organizations/roles-permissions", - "openhands/usage/cloud/organizations/settings" - ] - }, { "group": "Settings", "pages": [ @@ -421,6 +411,16 @@ } ] }, + { + "group": "Organizations", + "icon": "building", + "pages": [ + "openhands/usage/cloud/organizations/overview", + "openhands/usage/cloud/organizations/managing-members", + "openhands/usage/cloud/organizations/roles-permissions", + "openhands/usage/cloud/organizations/settings" + ] + }, { "group": "Automations (BETA)", "icon": "clock", From 312ab9c82999736e0fa7dbb4776ba810c2ff29e8 Mon Sep 17 00:00:00 2001 From: openhands Date: Tue, 28 Apr 2026 00:48:50 +0000 Subject: [PATCH 5/9] fix(orgs): fix navigation terminology and flow in managing-members and settings docs - managing-members.mdx: - Inviting: use 'Hover over profile icon' with direct 'Invite Organization Members' button (actual UI label) - Changing roles: consistent navigation using 'Org Members' nav label - Removing: fix incorrect nav flow ('organization settings page' + 'Members tab') to use 'Org Members' - settings.mdx: - Credits: clarify nav flow and use actual button label '+ Add' - Git routing: remove inaccurate steps (provider selection, org name entry, verification); orgs are listed automatically from connected identities - Monitoring: use bold for 'Organization' nav label for consistency Co-authored-by: openhands --- .../cloud/organizations/managing-members.mdx | 19 +++++++++---------- .../usage/cloud/organizations/settings.mdx | 18 ++++++++---------- 2 files changed, 17 insertions(+), 20 deletions(-) diff --git a/openhands/usage/cloud/organizations/managing-members.mdx b/openhands/usage/cloud/organizations/managing-members.mdx index 3e738dbf6..e68a22b4e 100644 --- a/openhands/usage/cloud/organizations/managing-members.mdx +++ b/openhands/usage/cloud/organizations/managing-members.mdx @@ -7,11 +7,10 @@ description: How to invite users and manage team members in your organization. To add a new member to your organization: -1. Click the profile icon in the lower left -2. Select the `Org Members` tab. -3. Click `Invite Org Member`. -4. Enter the email address of the user you want to invite. -5. Click `Add`. +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Click **Invite Organization Members** in the menu. +3. Enter the email address of the user you want to invite. +4. Click **Add**. The invited user will receive an email with instructions to accept the invitation and join your organization. Once they accept, they will be added as a **Member** by default. @@ -24,8 +23,8 @@ Once they accept, they will be added as a **Member** by default. After a user has joined your organization, an Admin or Owner can modify their role: -1. Click the profile icon in the lower left -2. Select the `Org Members` link +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Select **Org Members**. 3. Find the user whose role you want to change. 4. Click the role dropdown next to their name. 5. Select the new role: `Owner`, `Admin`, or `Member`. @@ -40,10 +39,10 @@ After a user has joined your organization, an Admin or Owner can modify their ro To remove a member from your organization: -1. Navigate to your organization's settings page. -2. Select the `Members` tab. +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Select **Org Members**. 3. Find the user you want to remove. -4. Click the `Remove` button next to their name. +4. Click the **Remove** button next to their name. 5. Confirm the removal. Removed members will lose access to the organization's shared resources immediately, but their private diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx index af6cb1e91..c37feeeef 100644 --- a/openhands/usage/cloud/organizations/settings.mdx +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -33,9 +33,9 @@ personal overrides. Organization credits are shared across all members. To add credits: -1. Click the profile icon in the lower left -2. Select the `Organization` link. -3. Click `Add`. +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Select **Organization**. +3. Click **+ Add**. 4. Choose the amount of credits to purchase. 5. Complete the payment process. @@ -43,7 +43,7 @@ Credits will be added to the organization's shared pool immediately and can be u ### Monitoring Usage -You can monitor credit usage from the `Organization` settings page, which shows: +You can monitor credit usage from the **Organization** settings page, which shows: - Current credit balance - Credit usage over time @@ -60,12 +60,10 @@ for repositories in that Git organization to be routed to your organization. Owners have the ability to claim a Git organization: -1. Click the profile icon in the lower left -2. Select the `Organization` link. -3. Under the `Git Conversation Routing` section, click `Claim` next to the Git organization to claim. -4. Select the Git provider (GitHub, GitLab, or Bitbucket). -5. Enter the name of the Git organization you want to claim. -6. Complete the verification process. +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Select **Organization**. +3. In the **Git Conversation Routing** section, your connected Git organizations are listed automatically. +4. Click **Claim** next to the Git organization you want to link to your OpenHands organization. You must have admin access to the Git organization to claim it. The verification process confirms your From 3dd9e2655c0d7b0c62fc79d371d91ed1e22fe7a3 Mon Sep 17 00:00:00 2001 From: openhands Date: Tue, 28 Apr 2026 00:49:28 +0000 Subject: [PATCH 6/9] fix(orgs): fix missing space before pipe in roles-permissions table Co-authored-by: openhands --- openhands/usage/cloud/organizations/roles-permissions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openhands/usage/cloud/organizations/roles-permissions.mdx b/openhands/usage/cloud/organizations/roles-permissions.mdx index d4626fbef..a9cbbbfd8 100644 --- a/openhands/usage/cloud/organizations/roles-permissions.mdx +++ b/openhands/usage/cloud/organizations/roles-permissions.mdx @@ -18,7 +18,7 @@ Organizations in OpenHands support three roles, each with different levels of ac | Elevate users to Admin role | | ✓ | ✓ | | Add credits | | ✓ | ✓ | | Modify LLM settings | | ✓ | ✓ | -| Elevate users to Owner role| | | ✓ | +| Elevate users to Owner role | | | ✓ | | Claim Git organizations | | | ✓ | | Delete organization | | | ✓ | From 072e568b7b60c3f8d73ae81193f5bf1bfbaef24c Mon Sep 17 00:00:00 2001 From: jpelletier1 <44589723+jpelletier1@users.noreply.github.com> Date: Mon, 4 May 2026 09:17:14 -0400 Subject: [PATCH 7/9] Update openhands/usage/cloud/organizations/settings.mdx Co-authored-by: OpenHands Bot --- openhands/usage/cloud/organizations/settings.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx index c37feeeef..296486afd 100644 --- a/openhands/usage/cloud/organizations/settings.mdx +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -16,7 +16,9 @@ includes LLM configurations, credits management, and Git organization claims. Organizations can define a default LLM provider and model that all members will use: -1. Navigate to your organization's settings page. +1. Hover over the profile icon in the lower left — an account menu will appear. +2. Select **Organization**. +3. Select the `LLM` tab. 2. Select the `LLM` tab. 3. Choose your preferred **LLM provider** from the available options. 4. Select the **model** you want to use as the default. From bf3e33edf1a704f7a0d16f508f76b32cd2cd00cf Mon Sep 17 00:00:00 2001 From: jpelletier1 <44589723+jpelletier1@users.noreply.github.com> Date: Mon, 4 May 2026 09:17:27 -0400 Subject: [PATCH 8/9] Update openhands/usage/cloud/organizations/settings.mdx Co-authored-by: OpenHands Bot --- openhands/usage/cloud/organizations/settings.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx index 296486afd..e389d288c 100644 --- a/openhands/usage/cloud/organizations/settings.mdx +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -64,7 +64,7 @@ Owners have the ability to claim a Git organization: 1. Hover over the profile icon in the lower left — an account menu will appear. 2. Select **Organization**. -3. In the **Git Conversation Routing** section, your connected Git organizations are listed automatically. +3. In the **Git Conversation Routing** section, Git organizations from your linked GitHub/GitLab accounts are listed automatically. 4. Click **Claim** next to the Git organization you want to link to your OpenHands organization. From 7125bc159fb0644f6f44592ff58c2960473f957f Mon Sep 17 00:00:00 2001 From: openhands Date: Mon, 4 May 2026 13:26:45 +0000 Subject: [PATCH 9/9] Update Monitoring Usage section to reference financial API endpoint Removed 'Credit usage over time' and 'Usage breakdown by member' from the Monitoring Usage section. Added reference to the API endpoint /api/organizations/{org_id}/members/financial for detailed user-level usage reporting. Co-authored-by: openhands --- openhands/usage/cloud/organizations/settings.mdx | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/openhands/usage/cloud/organizations/settings.mdx b/openhands/usage/cloud/organizations/settings.mdx index e389d288c..081c2c941 100644 --- a/openhands/usage/cloud/organizations/settings.mdx +++ b/openhands/usage/cloud/organizations/settings.mdx @@ -45,11 +45,15 @@ Credits will be added to the organization's shared pool immediately and can be u ### Monitoring Usage -You can monitor credit usage from the **Organization** settings page, which shows: +You can monitor credit usage from the **Organization** settings page, which shows the current credit balance. -- Current credit balance -- Credit usage over time -- Usage breakdown by member (for Admins and Owners) +For detailed usage reporting at the user level, use the API endpoint: + +``` +GET /api/organizations/{org_id}/members/financial +``` + +This endpoint provides financial usage data for all members within your organization. ## Claiming Git Organizations