| title | description |
|---|---|
How to manage community restrictions |
Follow this guide to restrict the {{ ml-platform-name }} resources and features available across all your community projects. |
{% note info %}
You can restrict the {{ ml-platform-name }} resources and features available across all your community projects only if you have the {{ roles-datasphere-communities-admin }} role in the community.
{% endnote %}
-
{% include ui-find-community %}
-
Select the community you want to configure the {{ ml-platform-name }} features for.
-
Go to the {{ ui-key.yc-ui-datasphere.common.restrictions }} tab.
-
Under {{ ui-key.yc-ui-datasphere.restrictions.project-mode }}:
- {{ ui-key.yc-ui-datasphere.restrictions.JUPYTER_TOKEN }}: Enables working with projects from any local IDE that supports the use of remote {{ jlab }} servers.
- {{ ui-key.yc-ui-datasphere.restrictions.DEDICATED_INSTANCE_COUNT }}: Number of VMs available in community projects.
-
Under {{ ui-key.yc-ui-datasphere.common.resources }}:
- {{ ui-key.yc-ui-datasphere.restrictions.CHANGING_DISK_SIZE }}: Enables project storage resizing.
- {{ ui-key.yc-ui-datasphere.restrictions.NODES_AND_ALIASES }}: Enables service deployment using nodes and aliases in community projects.
- {{ ui-key.yc-ui-datasphere.restrictions.DATAPROC_TEMPLATES }}: Enables the use of {{ dataproc-name }} templates in community projects.
- {{ ui-key.yc-ui-datasphere.common.datasets }}: Enables creating datasets in community projects.
-
Under {{ ui-key.yc-ui-datasphere.spaces-page.configurations }}, you can select computing resource configurations that will available across all your community projects.