Which action in Fusion enables resource sharing, such as connections, data stores, and keys?

In collaborative technical environments, a "team" is the designated construct for a group of users to share common resources for a specific project or function. This includes sharing assets like data store connections, API keys, and other configuration details necessary for joint development and analysis. Creating a team provides a dedicated workspace where these shared resources can be managed and accessed by all team members, streamlining workflows and ensuring consistency. This model separates resource management from broader, role-based permissions (groups) or top-level account administration (organizations).

A. Create a new group: In the Adobe ecosystem, "groups" (specifically User Groups in the Admin Console) are primarily used for managing user permissions and assigning access to products and services, not for sharing specific technical assets like connections or keys.
C. Create a new organization: An "organization" (or IMS Org) is the top-level entity that represents an entire company's relationship with Adobe. Creating a new organization would segregate users and resources, which is the opposite of sharing them among collaborators within an existing company structure.

1. General Principle of Teams in Collaborative Software (Applicable Logic): While a direct document for an Adobe product named "Fusion" using "teams" is not available, the concept aligns with standard software engineering and data science platform design. Collaborative platforms use teams or projects as a mechanism to scope and share resources. For example, in Adobe Experience Platform, a similar concept of sandboxes is used for isolation, but for collaboration, project-based sharing is a common paradigm. The choice of "team" is the most logical fit for the described function.

2. Role of an Organization (Disproves Option C): Adobe, Admin Console overview. Adobe Help Center. This document explains that an organization is the master account for a company to manage its Adobe product licenses and users. It is the container for all assets, making the creation of a new one an act of segregation, not sharing. (Accessed from the official Adobe HelpX documentation).

3. Role of a Group (Disproves Option A): Adobe, Manage user groups. Adobe Admin Console User Guide. This guide details that user groups are for efficiently managing product permissions for multiple users at once. Their function is centered on access control and entitlement, not the sharing of configurable resources like data connections or API keys within a project workspace. (Accessed from the official Adobe HelpX documentation).