# Error 135 "You cannot have access to another user" **URL:** \ **Category:** API and Webhooks\ **Tags:** api\ **Created:** [December 3, 2025, 12:32am UTC](https://devforum.zoom.us/t/error-135-you-cannot-have-access-to-another-user/139081 "2025-12-03T00:32:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ProLegalAPI](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@ProLegalAPI](https://devforum.zoom.us/u/ProLegalAPI)\ **Post date:** [December 3, 2025, 12:32am UTC](https://devforum.zoom.us/t/error-135-you-cannot-have-access-to-another-user/139081/1 "2025-12-03T00:32:33Z")
**API Endpoint(s) and/or Zoom API Event(s)** _Sending SMS_ **Description** I found another topic ( SMS API Error 135: “You cannot have access to another user” with Admin-Managed App ) from a few months ago with this same error. Using the API, this can’t be right, right? I’m building an app that will send SMS from a group SMS number (i.e. not assigned to a user, but rather assigned to an auto receptionist). If I have to pay for a user to do this, that’s insane. Plus, I am not sure how I’d even set that up given the user would have to have a number that is assigned to an auto receptionist. Please advise. This feature was a top three reason we moved to Zoom phone and I was told this was possible with the API. ---
**Author:** ![ProLegalAPI](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@ProLegalAPI](https://devforum.zoom.us/u/ProLegalAPI)\ **Post date:** [December 3, 2025, 4:10pm UTC](https://devforum.zoom.us/t/error-135-you-cannot-have-access-to-another-user/139081/4 "2025-12-03T16:10:37Z")
Thanks. That does seem sort of crazy and really limits the ability to be creative with how the system is used. Now I’m doing a bunch of circular workarounds (including having to build my own sending solution since I can’t use the Zoom App to manage this group SMS box) just to make it work.