Managing Teams

In many situations the concept of an Organization is sufficient to manage your internal resources (people and assets) as well as agreements and usage requests by outside groups. However as the number of projects and people involved expands, being able to further organize and limit the visibility of assets can be important for simplicity and compliance purposes. To assist with this, Teams can be created within your organization.

Organization vs Team

A member of an organization can be in one or more teams. By default, each organization has exactly one team and all of the users are simply members of that same team.

Once a second team has been created, members of the organization can be added to that team or not by the team administrators. Any asset created with only Team visibility will by default only be visible to the members of that team. Assets can be made visible to other teams via an Agreement, or by making the asset’s visibility Public.

Similarly, Processes and Audit records for operations performed by members of the team to members of that same team. There is no way to share Processes or Audit records with other teams.

Permissions are applied on a team by team basis. For example a single user could be granted the ability to Manage Agreements for one team, but not for other teams.

Although the visibility is segregated, the actual storage and computational resources for all teams within an organization is the same Access Point.

Why Use Teams Instead of Independent Organizations?

Using the same Access Point for multiple teams simplifies the setup and maintenance tasks. Only a single virtual machine is needed, firewall rules need only be set up once, and upgrades are simple.

Additionally, users can easily be added or removed from teams at will. An organization admin can change this membership at any time. While assets can be used for joint operations between different organizations, only members of the same organization are able to access output assets.

When to Use Separate Organizations instead of Teams

Since an organization uses the same access point for all Teams and that access point only has a single attached storage associated with it, Teams cannot satisfy data localization requirements for an entity that spans multiple countries.

Learning More

If you are interested in taking advantage of Teams for your organization, talk to your TripleBlind representative for more information. We’d be happy to help you setup your second team and get you started working with Teams.