HyperAIHyperAI

Organization Resource Management

Each organization is an independent namespace, which means "Data Repositories" and "Computing Containers" have independent access permissions under the organization. At the same time, "Storage" and "Computing Resources" under the organization are also independent.

Organization Resource Permissions

Permission Description

Click on any computing container under the organization and switch to the "Settings" page to see the resource visibility settings.

Resource visibility under an organization is divided into three types:

Resource VisibilityDescription
Personal VisibleSet the container as private; this operation will make the container invisible to other members within the organization
Organization Read-onlyIn this mode, the project will be read-only within the organization; organization members will have read-only permissions for the project and cannot create new content under this resource
Organization Read-writeIn this mode, the project will be readable and writable within the organization; organization members will have read-write permissions for the project, can create new content under the project, and have edit and delete permissions for content they create

Similar to "Computing Containers," "Data Repositories" also have the permissions shown above.

:::caution Note Organization administrators can directly modify resource visibility. :::

Default Permissions

The permissions when creating resources (computing containers, data repositories, etc.) within an organization are derived from the default resource permissions in "Organization Settings." Organization administrators can modify the default resource permissions in "Organization Settings."

Use Cases

Teaching Scenario

A teacher creates an organization and becomes the organization owner, inviting students to join the organization.

Set the default resource permission to "Personal Visible" to ensure each student can only see their own computing containers and not those of other students.

The teacher creates a "Data Repository" and sets the permission to "Organization Read-only" to ensure students can use the data repository while preventing data loss due to accidental operations by others.

The teacher creates a "Computing Container" and sets the permission to "Organization Read-only" as teaching materials. Students can clone it into their own computing containers using the "Clone" function.

Project Collaboration

Two members within an organization work on the same project and want to access each other's execution content.

Member A creates a "Data Repository" and sets the permission to "Organization Read-write" to ensure not only they can edit data content, but also allow Member B to add new data versions.

Member B creates a "Computing Container" and sets the permission to "Organization Read-write," so both Member A and Member B can create executions in the same computing container and access each other's running execution content. Additionally, JupyterLab itself supports real-time collaboration, allowing Member A and Member B to see each other's operations when they both open JupyterLab simultaneously.

Organization "Resource Usage"

When creating resources (computing containers, data repositories, etc.) under an organization, storage resource and computing usage will be recorded in the organization's "Resource Usage."

Similar to "Resource Usage" under personal accounts:

  • "Overview" displays the organization's total storage resources, used resource quantity, and remaining available resources;
  • "Usage" records the type, date, product type used (computing resource type, storage space), duration of use, and storage space consumption for each task under the organization;
  • "Resource Change Details" records the change status of each resource (for example: subscribing to storage space);
  • "Quota Limits" records the quota limits for each resource, which are shared among organization members;

Organization "Finance Center"

Each organization has an independent financial account that is not shared with the organization creator's account. This means the balance under a personal account cannot be used for the organization account.