Project Structure and Permissions
WhaTap manages monitoring targets through a three-level hierarchy of projects, groups, and organizations. You can invite members to each level and assign permissions to set appropriate access scopes based on their roles.
Hierarchical structure
Project
The basic unit of monitoring. Monitoring targets are separated and member permissions are managed on a per-project basis.
Projects are categorized by monitoring agent type, such as application, server, and container.
Within the same agent type, you can also split projects by purpose, such as Front, Gateway, and API.
Group
A unit for managing multiple projects together. Adding members to a group applies the same permissions to all projects within the group. Members with permissions granted only at the project level can monitor only that project.
Organization
The top-level unit for managing multiple groups together. In most cases, projects and groups alone are sufficient.
For managed service provider (MSP) businesses that manage multiple client companies as groups, organizations allow you to consolidate multiple groups under a single management structure. Granting permissions to each group's members enables independent group management.
Member permission inheritance
Member permissions from a parent level are automatically inherited by child levels. For example, Group B under Organization A inherits Organization A's member permissions, and Project C under Group B inherits Group B's member permissions. Parent-level permissions are retained after inheritance.
Member permissions
You can grant different permissions to members for each project, group, and organization. For details on the ten permissions and how to change them, see Member Permissions.