--- title: "Organization Not Allowed Error When Joining a Remote Support Session" slug: "organization-not-allowed" updated: 2026-11-04T15:44:54Z published: 2026-11-04T15:44:54Z canonical: "docs.screenmeet.com/organization-not-allowed" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt > Use this file to discover all available pages before exploring further. # Organization Not Allowed Error When Joining a Remote Support Session This article explains why the **Organization Not Allowed** message appears when joining a ScreenMeet Remote Support session and how to resolve it on Windows and macOS devices. This article is intended for ScreenMeet Administrators and IT or Network teams who manage ScreenMeet deployments on end-user devices. --- When an end user attempts to join a ScreenMeet Remote Support session, the session does not connect and the following message appears: **Organization Not Allowed** The organization restriction applies to both the pre-installed ScreenMeet client and the one-time download client. This is intentional, so that ScreenMeet respects the restriction whenever it is configured on the device. The setting is stored on the device, not in the ScreenMeet client, so only the device configuration determines which organizations are allowed. One Org ID per Environment ScreenMeet creates a separate organization for each environment you configure it in. Each sandbox or test environment will have its own Org ID, and each one must be added to the allowed list individually. --- ### Resolution To resolve the error, add the ScreenMeet Org ID that started the session to the device's allowed organization list. If you do not manage ScreenMeet deployments, contact your ScreenMeet Administrator or Network team and provide the Org ID that needs to be allowed. Keep the following in mind when configuring the allowed list: - The allowed organization list can be set when installing or updating ScreenMeet, or manually on the device. - Multiple Org IDs are supported. Separate each Org ID with a comma and no spaces, for example `1234,5678`. - Setting a new list replaces the existing list. Include every Org ID that should remain allowed. #### Windows - To review the current configuration, open **Registry Editor** and go to the following path: `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ScreenMeet` - To update the allowed list, install or update ScreenMeet, configure the values manually on the device, or run a script that sets the following installer parameters: `ORGRESTRICT="True" ORGRESTRICTLIST="1234,5678"` - Replace `1234,5678` with the ScreenMeet Org IDs you want to allow. #### macOS - Run the following commands in **Terminal**. - To view the Org IDs currently allowed on the device, run: `getAllowedOrgIDs` - To set the allowed list, run: `setAllowedOrgIDs=1234,5678` - Replace `1234,5678` with the ScreenMeet Org IDs you want to allow. Clearing the Allowed List Running `setAllowedOrgIDs` with no value clears the list and removes the organization restriction from the device. The device then accepts sessions from any ScreenMeet organization. --- ### If Issue Persists If the message still appears after updating the allowed list, check the following: - Confirm the Org ID matches the environment that started the session, not a different sandbox or production org. - Confirm there are no spaces or extra characters in the comma-separated list. - Confirm the updated values are present in the registry (Windows) or returned by `getAllowedOrgIDs` (macOS). --- ### Related Articles - [ScreenMeet Remote Support Windows Installer Parameters](/docs/organization-not-allowed#) - [ScreenMeet Remote Support macOS Configuration Options](/docs/organization-not-allowed#)