[Yandex Cloud documentation](../../index.md) > [Yandex DataSphere](../index.md) > [Concepts](index.md) > Communities

# Communities in DataSphere

_Communities_ represent a way to organize team work in DataSphere. A community determines the scope of projects and resources and helps set up team activities.

Roles determine what the community members can do. A community member may be a _developer_, _editor_, or _administrator_. For a full list of community members, see the **Members** tab. Developers can create projects and their resources, run calculations in the IDE, and share resources in the community. Editors can change [settings](../operations/community/manage-community-config.md). Community administrators can invite new members to the community and manage their roles. For more information about roles in DataSphere, see [this article](../security/index.md).

You can attach to a community [any link](../operations/community/link-channel.md) you want to share with its members.

To create resources and run projects in the IDE, link a Yandex Cloud [billing account](../../billing/concepts/billing-account.md) to the community. To learn how to do it, see [Linking a billing account](../operations/community/link-ba.md).

## Sharing DataSphere resources {#share}

DataSphere resources are assigned to the [project](project.md) in which they were created. However, communities enable you to use resources from one project in another. This helps you save your time and money on recreating resources.

A project editor can use the **Access** tab on the resource page to share a project resource in a community where they are a developer. The resource will then appear among the community resources and all community members will be able to use it in their projects.

> For example, Julia works with multiple teams and belongs to their communities with different access permissions:
  
  * In the <q>Cat lovers</q> community: `Admin` (the `datasphere.communities.admin` role).
  * In the <q>Counting fences</q> community: `Developer` (the `datasphere.communities.developer` role).
  * In the <q>Top secret</q> community: `Viewer` (the `datasphere.communities.viewer` role), but with the `Editor` permissions in <q>Project_111</q> of this community (the `datasphere.community-projects.editor` role).
  
  Julia can:
  
  * Share the resources of any <q>Cat lovers</q> community's project within this community.
  * Share the resources of any <q>Cat lovers</q> community's project in the <q>Counting fences</q> community.
  * Publish the <q>Project_111</q> resources in the <q>Cat lovers</q> and <q>Counting fences</q> communities, but cannot share them in the <q>Top secret</q> community.

{% note info %}

You can only share resources within a single organization, between communities created in the same [availability zone](../../overview/concepts/geo-scope.md).

{% endnote %}

#### Useful links {#see-also}

* [Resource relationships in DataSphere](resource-model.md)
* [Access management in DataSphere](../security/index.md)
* [Access management in Yandex Identity Hub](../../organization/security/index.md)
* [Managing a community](../operations/index.md#community)
* [Linking a billing account](../operations/community/link-ba.md)
* [Setting up a student community](../tutorials/community-for-students.md)
* [How to automate project setup using APIs](../tutorials/automation-community-settings.md)