---
title: Manage organizations
description: How to create an organization if you wish to restrict user access to workers. You can prevent members from sharing the organization's projects to outside users or groups.

---
# Manage organizations {: #manage-organizations }

!!! info "Required permission"
    “Can manage users”

Set an organization for users if you wish to restrict access to workers. See the [overview](admin-overview#what-are-organizations?) for a description of the organization functionality in DataRobot. Some notes on using organizations:

* Organization membership is not a requirement for DataRobot users.

* Users can belong to only one organization at a time; if you add a user to a new organization, they are automatically removed from the existing organization.

* Assigning a parent organization to a group limits <em>group</em> membership to members of the parent organization (i.e., you are restricted to adding only users who are members of that parent organization).

* You cannot change a group's parent organization once assigned.

## Understand restricted sharing {: #understand-restricted-sharing }

You can use a "restricted sharing" setting to prevent organization members from sharing projects *from* the organization to users or groups outside of it. This setting does not prevent users outside the organization from sharing projects *to* the organization. Users outside of a "restricted sharing" organization can share projects with any members and groups.

After creating an organization, you can change its restricted sharing policy from the the organization profile. If you set **Restrict sharing to organization members** after the organization was created, any project sharing that already exists is not affected; making this change only prevents the ability to start new project sharing with users or groups outside of the organization.


## Create organizations {: #create-organizations }

Follow these steps to create an organization:

1. Expand the profile icon located in the upper right and click **APP ADMIN > Organizations**. The displayed page lists all existing organizations. From here you create and manage organizations.

2. Click **Create new organization**.

3. In the displayed dialog, enter a name and the [number of workers](admin-overview#what-workers) to assign to the organization.

4. If you want to [restrict users](#restrict-orgs) in this organization to sharing projects only with other users and groups within this organization, select **Restrict sharing to organization members**.

	 ![](images/admin-add-org.png)

5. Click **Create Organization**. The **All Organizations** profile lists the new organization.

6. Click an organization to see its profile. In the below image, for example, the new ACME3 organization is allocated a maximum of 14 workers and members of the organization can share projects with users and groups outside of the ACME3 organization.

	![](images/admin-orgprofile.png)

!!! note
    The worker resource allocation ("Workers limit") is independent from your cluster configuration. To avoid worker resource issues, don’t oversubscribe the physical capacity of the cluster.

## Add users to organizations {: #add-users-to-organizations }

You can add one or more users to (or remove users from) any defined organization using the **Organizations** pages. You can add or remove individual users from the [**User Profile > Membership**](manage-users#manage-groups-and-organization-membership) page.

1. Open the **Organizations** page and select the organization to which you want to add a user. The profile page for that organization opens.

2. Click **Members** to list all members of that organization.

	![](images/admin-orgs-members.png)

3. Click **Add a user** and from the displayed dialog, start typing the name of a user to add. As you type, DataRobot shows usernames containing those characters.

4. Select the intended user and repeat for each user you want to add. When done, click **Add users**.

The displayed list shows all members of the organization and information for each, including first name, last name, and status ([active/inactive](manage-users#user-accounts-disable) in DataRobot).

## Delete organizations {: #delete-organizations }

You can only delete an organization once all the members have been removed. Any projects previously shared with the organization (and therefore, to each user in the organization), are no longer shared with those (ex) members. If needed, re-share projects with individual users.

To delete an organization:

1. Expand the profile icon located in the upper right and click **APP ADMIN > Manage Organizations**. In the displayed list of organizations, check the **Total Members** column for the organization you want to delete to determine whether there are members assigned it. If the organization has members, you must remove them before you can delete the organization.

2. If the organization has members, do the following:

    * Select that organization to open its profile and click **Members**.
    * From **Menu** click **Select All**, then click **Delete selected**.

	     ![](images/admin-deleteselected-menu.png)

    * In the displayed **Confirm Removal** window, click **Remove members**. Removed members are removed from the list of organizations only.

3. When the organization has no members, view the **Organizations** page and do one of the following:

    * If you want to delete a single organization&mdash;locate the organization, select the **Actions** menu, and click **Delete organization**. (You could also delete the organization from the organization profile, using **Actions** > **Delete**.)
    * If you want to delete multiple organizations&mdash;select the check boxes for those organizations (or select the check box next to the **Organization** heading), click **Menu**, and then select **Delete selected**.

4. In the displayed **Confirm Delete** window, click **Delete organization** (or **Delete organizations** if shown). Deleted organizations are removed from the list of organizations.

##  Configure organization permissions {: #configure-organization-permissions }

You can configure permissions and apply them to all users in an existing organization in addition to managing each user individually. This allows for easier tracking and management of permissions for larger organizations.

!!! note
    Note that a user's effective permissions are the union of those granted to their organization, any user groups they are a member of, and permissions granted to the user directly.  A user who is added to an organization obtains all permissions of that organization. A user who is removed from an organization does not maintain any permissions that were granted to them by the organization. However, a user may still have the permissions granted by that organization if a group they belong to also grants those permissions.

1. To configure permissions for an organization, select it from the **Organizations** page and navigate to the **Permissions** tab.

	![](images/org-permission-1.png)

2. The **Permissions** tab displays the premium products, optional products, public preview features, and admin settings available for configuration for your organization. Select the desired permissions to grant your organization from the list.

3. When you have finished selecting the desired permissions for your organization, click **Save Changes**.

Once saved, all existing users in your organization and those added to it in the future are granted the configured permissions. A user can view their permissions on the **Settings** page. Hover over a permission to see what group(s) or organization(s) enabled it.

![](images/group-permission-3.png)


## Manage custom model resource allocation {: #manage-custom-model-resource-allocation }

For DataRobot MLOps users, you can determine the [resources allocated for each custom inference model](custom-inf-model#manage-custom) within an organization. Configuring these resources facilitates smooth deployment and minimizes potential environment errors in production.

To manage these resources for an organization, navigate to the organization's **Profile** page and find **Custom model resource allocation settings**. Configure the fields:

![](images/resource-4.png)

|    Resource    | Description |
|----------------|---------------------------|
| Desired memory | Determines the minimum reserved memory for the Docker container used by the custom inference model.|
| Maximum memory | Determines the maximum amount of memory that may be allocated for a custom inference model. Note that if a model allocates more than the configured maximum memory value, it is evicted by the system. If this occurs during testing, the test is marked as a failure. If this occurs when the model is deployed, the model is automatically launched again by kubernetes.  |
| Maximum replicas | Sets the maximum number of replicas executed in parallel to balance workloads when a custom model is running. |


When you have fully configured the resource settings, click **Save**.

## Manage execution environment limits {: #manage-execution-environment-limits }

{% include 'includes/ex-env-limits.md' %}

1. Click your profile avatar (or the default avatar ![](images/icon-gen-settings.png)) in the upper-right corner of DataRobot, and then, under **APP ADMIN**, click **Organizations**.

2. To configure permissions for an organization, select it from the **Organizations** page and then click **Permissions**.

	![](images/org-permission-1.png)

    !!! important
		If you access the **Members** tab to set these permissions, you are setting the permissions on an individual user level, not the organization level.

3. On the **Permissions** tab, click **Platform**, and then click **Admin Controls**.

    ![](images/platform-admin-controls.png)

4. Under **Admin Controls**, set either or both of the following settings:

    * **Execution Environments limit**: The maximum number of custom model execution environments a user in this organization can add. This limit setting can't exceed 999.

    * **Execution Environments versions limit**: The maximum number of versions a user in this organization can add to each custom model execution environment. This limit setting can't exceed 999.

        ![](images/execution-env-controls.png)

5. Click **Save changes**.