Organizations in allow you to have many users and networks and manage who can do what with role based permissions.

A role is a collection of permissions. A user can have many roles.

If you have the appropriate permissions, you will be able to see and manage all the roles in an organization.

In a role, each permission can either be granted, denied or not set. If a permission is granted, the user with the role will have that permission. If the permmission is denied, then even if the user has that permission from another role, it will be denied - the net result is that the user will not have that permission. If a permission is not set, then the user with that role will not have that permission unless it is granted by another role assigned to that user.

Organizations are made up of many users. Each user can be assigned to a network, and each user can have their own set of permissions granted via roles.

With the appropriate permissions, you are able to add, or removed users to/from the organization, and assign users to networks.

Devices can be used instead of users if whatever is attached to the devices can't or shouldn't have access to argustak.com. Some examples of when to use devices instead of users is if for example, you have TAK Tracker installed on a container, or a search dog. Devices count towards seat usage.

In organizations, networks represent a colleciton of users. All those users devices will communicate with each other

You can federate networks within the same organization together with the correct permissions.

You can also federate networks with other organizations using codes, on the network details -> federated networks tab.

Network Certificates

With a network certificate, many devices can connect to the given network using the one network certifcate. The maximum number of devices that can connect at the same time count towards seat usage.