Skip to main content
Managing Teams

How do we keep activity from multiple groups separate?

Updated over a week ago

Managing a team, or multiple teams, is part of the enterprise platform. There are a few options available depending on the needs of your organization. Usually, the distinction between these options boils down to the needed level of data security.


Accounts

The first way we can compartmentalize data is by spinning off a separate account. This is a hard wall that users will not be able to see the other data unless they are added to the account and given the correct permissions. This is the most secure way to separate data. Sensitive teams, like SWAT or Nuclear Inspections, are often set up in a separate account.
โ€‹

Tags


Tagging will be utilized in order to manage multiple teams, or even multiple use cases, on a single account. Tags are flexible throughout the account, and you can learn more about them here. In the example below, the team is separated by the state they operate in.

In the example below, this "Region" tag applies to users, missions, flights, and aircraft so we can easily filter down to those individual teams' data, or remove the tag and see everything combined in more of a global dashboard view.

Team admins or chief pilots can then set their views and limit it to only data for their team by selecting the appropriate team or department tag.

Permissions

This can work across teams on multiple accounts or with multiple teams on one account. This is not as restrictive as the account separation, and in some cases, pilots may be able to see certain aircraft info or authorization details on the airspace map from users that aren't on their "team".

This approach, along with tags, works well if the main purpose of compartmentalizing is for reporting and team metrics versus isolating the data for security.

Did this answer your question?