--- title: "Add New User to Existing Org" url: https://docs.catalyst.zoho.com/en/sdk/python/v1/cloud-scale/authentication/add-new-user-to-existing-org/ description: "This page describes the method to add a new user to the existing organisation in your Python application with sample code snippets." last_updated: 2025-11-19T15:07:41Z service: Cloud Scale type: general related_links: - name: "Add New User to Existing Org - API" url: /en/api/code-reference/cloud-scale/authentication/add-user-to-existing-org/#AddaNewUsertoanExistingOrganization - name: "Authentication Help" url: /en/cloud-scale/help/authentication/introduction - name: "SDK Scopes" url: /en/sdk/python/v1/sdk-scopes --- # Add a New User to an Existing Organization You can add an end-user to an existing organization without creating a new organization for them. This can be done by providing the [**OrgID**](https://docs.catalyst.zoho.com/en/getting-started/catalyst-organizations/) of the organization that the user must be added to. When the user has signed up, unique identification values such as [ZUID and User ID](https://docs.catalyst.zoho.com/en/cloud-scale/help/authentication/user-management/users/introduction/#authentication-and-user-basics) are created for them by Catalyst. > **Note :** * You must provide the values for `org_id`, `email_id`, `last_name` mandatorily to add a user to an existing organization. * You can obtain the ZAID from the [Environment settings](https://docs.catalyst.zoho.com/en/deployment-and-billing/environments/introduction) in your Catalyst console. * You can also add them to a role by providing the `role_id`, which you can obtain from the Roles section in Authentication in the Catalyst console. * When inviting a new user, you can configure the sender's email address, subject and the email message. You must add the email address in the [Catalyst Mail Component](https://docs.catalyst.zoho.com/en/cloud-scale/help/mail/email-configuration/) and get it verified before using it in the SDK code. ## Create a Dictionary Before you add a new end-user to your Catalyst application, you must create a dictionary that contains the registration details of the particular user, as shown below. You can then pass the configured dictionary to the method that handles the user signup process. ```python #Create a dictionary signup_config = { "platform_type": "web", "zaid": "1008807534", "template_details": { "senders_mail": "dogogetu@tutuapp.bid", "subject": "Welcome to %APP_NAME%", "message": "<p>Hello ,</p> <p>Follow this link to join in %APP_NAME% .</p> <p><a href='%LINK%'>%LINK%</a></p> <p>If you didn’t ask to join the application, you can ignore this email.</p> <p>Thanks,</p> <p>Your %APP_NAME% team</p>", }, } user_details = { "first_name": "Amelia", "last_name": "Burrows", "email_id": "amelia.burrows@gmail.com", "org_id": "1005641456", } ``` ### Add a New User to Existing Org You can add a new end-user to an existing organization using the code below. You must pass the dictionary you created in the previous section as an argument to the `add_user_to_org()` method. This method handles the user sign-up process and returns a response. > **Note :** You will only be able to add 25 users in your application in the [development environment](https://docs.catalyst.zoho.com/en/deployment-and-billing/environments/development-environment). After you deploy your application to production, you can include any number of end-users in it. To know more about the component instance `authentication_service` used below, please refer to [this section](https://docs.catalyst.zoho.com/en/sdk/python/v1/cloud-scale/authentication/get-component-instance/). **Parameters Used**
| Parameter Name | Data Type | Definition |
|---|---|---|
| `signup_config` | Object | A **Mandatory** parameter. Will store the user registration details, including the application platform, ZAID, and the email information to be sent after registration. |
| `user_details` | Object | A **Mandatory** parameter. Will hold the user registration details such as first name, last name, email ID and ID of the organization to which the user has to be registered. |