Organization Service

the organization service manages organizations, environments and teams and serves as fundamental level of access management across all nativewaves services and apis, access is managed using a hierarchical resource membership and role system this system enables granular authorization structures and flexible access control here's how it works users can be members of organizations and hold specific roles within those organizations for example, a user can be a member of an organization with the role of "admin" when the user accesses a child resource, such as an environment, the nativewaves platform recognizes their admin access to the parent resource (organization) as a result, the user is granted relevant privileges and permissions for the child resource in addition, users can also be members of specific environments without direct membership in the parent organization if a user, who is solely a member of an environment, attempts to access organization related information, such as listing available organizations in the console, the nativewaves platform understands the user's active membership to the child resource it grants limited privileges to allow the user to perform the specific task, such as listing the organization for more in depth information regarding the rest api of this service, we encourage you to check the swagger api documentation this comprehensive page outlines the various endpoints, parameters, and responses of the api organizations a user account is always associated with you individually and is not governed by any organization you have the option to be a member of multiple organizations, either by creating them yourself or by receiving invitations to join existing ones organizations serve as the fundamental level of access management, with all resources belonging to a particular organization billing information and resource usage are calculated based on the organization as a whole, rather than on an individual user basis the user who initially creates an organization assumes the role of the organization owner as the owner, they possess the most extensive privileges, including the ability to delete the organization once the organization is created, it is possible to add other members to the organization environments environments serve as the primary means of managing resources in different contexts that are independent of organization management, such as teams, members, and related organization settings the main purpose of environments is to group resources and provide a convenient approach to configuring environments for different contexts, such as a production environment and test or development environments tailored to your specific infrastructure needs teams teams allow you to manage access rights to certain resources in a grouped manner when granting member access to a resource, teams can be included alongside individual users this ensures that every team member receives the same membership status for that resource furthermore, teams can themselves be members of other teams, resulting in the propagation of all related resource membership statuses from parent teams to all child teams and their respective members