Manage communities

A community is a grouping of other communities (subcommunities) and domains. It often corresponds to the functional divisions in a company and works best if it is aligned with a company's governance organization.

Important 

Choose an option below to explore the documentation for the latest user interface (UI) or the classic UI.

Out-of-the-box communities

Collibra uses the following out-of-the-box communities, all of which are system-managed, meaning that they are managed by Collibra and you can't move or delete them. If needed, you can hide them by restricting their view permissions.

Community name System-managed Community ID
AI Governance Green check icon Yes 00000000-0000-0000-0001-000100000004
Asset change management Red close icon No c0e00000-0000-0000-0007-000000000000
Business Analysts Community Green check icon Yes 00000000-0000-0000-0001-000100000001
CCPA building blocks Red close icon No c0e00000-0000-0000-0007-000000000003
Data privacy building blocks Red close icon No c0e00000-0000-0000-0007-000000000001
GDPR building blocks Red close icon No c0e00000-0000-0000-0007-000000000002
Privacy content Red close icon No c0e00000-0000-0000-0007-000000000004
Schemas Green check icon Yes 00000000-0000-0000-0001-000100000002
Data Governance Council Green check icon Yes Randomly generated ID

Permissions

The following table contains the resource permissions required to manage a community.

Note If you have the Resources > Manage all resources global permission, you can perform all the actions listed in the table, even without the specific resource permissions.
Action Resource permission
Create a community

Community > Add
Edit a community name

Community > Update
Move a custom community to a parent community
  • Community > Update (on the custom community)
  • Community > Add (on the parent community)
Delete a custom community

Community > Remove

Create a community

You can create your own community at the top level of your organization or under another community (as a subcommunity).

Prerequisites

You have a resource role with the Community > Add resource permission.

Steps
  1. On the main toolbar, click Plus icon.
    The Create dialog box appears.
  2. Click the Organization tab.
  3. In the Community section, select Community.
    The Create Community dialog box appears.
  4. Enter the required information.
    FieldDescription
    CommunityOptional parent community under which the new community will be located.
    Tip 
    • If you are currently on a community page, this field shows that community by default.

    • If you select a community in this field, the new community is created (as a subcommunity) under the selected community.

    • If you leave this field empty, the new community is created (as a community) at the top level of your organization.

    Community name

    		Name of the new community.
    Tip 
    • You can create multiple communities together. To do so, enter the first name, click the drop-down or press Enter, and then enter the next name.
    • Community names must be globally unique. You can't create identically named communities even if their parent communities are different.
  5. Click Create.

Edit a community name

You can change the name of any community.

Prerequisites

You have a resource role with the Community > Update resource permission.

Steps
  1. Open the community.
  2. Click Actions → Edit.Click → Edit.
    The Edit Community dialog box appears.
  3. In the Name field, enter the new name for the community.
    Note Community names must be globally unique.
  4. Click Save.
Tip You can also edit the community name via the organization table on the Overview tab of the community page. To do so, double-click the Name cell of the community, enter the new name, and then click .

Move a community

Note System-managed communities can't be moved.

If a custom community has a parent community, you can change its parent community by moving the custom community to a different parent community. If a community is moved to a parent community in another scope, the assignment of the community's assets may change. If moving a community causes a conflict of scopes, the conflicting resources are removed from their original scope.

If a custom community doesn't have a parent community (meaning that it is a top-level community), you can move the custom community to a parent community to make it a subcommunity.

Prerequisites
  • You have a resource role with the Community > Update resource permission on the community you want to move.
  • You have a resource role with the Community > Add resource permission on the parent community to which you want to move the community.
Steps
  1. Open the community.
  2. Click Actions → Move.Click → Move.
    The Move Community dialog box appears.
  3. In the Name field, enter the name of the new parent community.
    Note Community names must be unique within their parent community. If you try to move the community to a parent community that already contains a community with the same name, an error message appears after you click Save.
  4. Click Save.

Delete a community

Note System-managed communities can't be deleted.

You can delete a custom community if you no longer need it. Deleting a community also deletes its views, domains, and assets.

Prerequisites

You have a resource role with the Community > Remove resource permission.

Steps
  1. Open the community.
  2. Click Actions → Delete.Click → Delete.

Related topics

  • Add domains to a community by creating a new domain or moving an existing domain.
  • Add a responsibility to assign a resource role to a user or group for a community