Use cases

This section describes typical use cases for Neutree’s user management features to help you configure user permissions according to your actual business needs.

Single administrator

Suitable for small teams and individual developers where only one administrator is needed to handle all operations. In this case, the initial administrator account of Neutree is sufficient.

Permission separation

Suitable for medium and large teams that need to separate permissions based on job responsibilities to improve system security and management standardization. You can create different types of roles to separate responsibilities such as platform administration, business development, and audit monitoring:

• Administrator: Global administrator permissions, responsible for overall platform management and maintenance.
• Developer: Inference endpoint operation permissions in specific workspaces, responsible for model deployment and inference service management.
• Auditor: Global read-only permissions, responsible for monitoring and auditing platform activities, with no modification permissions.

Example

1. The administrator creates multiple users on the Users page:
   • User A
   • User B
2. The administrator creates custom roles on the Roles page:
   • A Developer role with permissions to create, edit, and delete inference endpoints.
   • An Auditor role with view-only permissions for all modules.
3. On the Workspace Policies page, configure the corresponding permissions for different users:
   • Assign User A a global policy with the Developer role.
   • Assign User B a global policy with the Auditor role.

Multi-tenant isolation

Suitable for scenarios where independent AI services must be provided to different teams, departments, or external customers while ensuring data isolation and resource security. You can use workspaces to achieve multi-tenant isolation. Each tenant has its own independent resource and model space, ensuring that different businesses do not interfere with each other and that data is securely controlled.

• Administrator: Has global administrator permissions, responsible for building the platform infrastructure and multi-tenant architecture.
• Tenant A: Has specific operation permissions only within Workspace A.
• Tenant B: Has specific operation permissions only within Workspace B.

Example

1. The administrator creates multiple workspaces on the Workspaces page:
   • Workspace A
   • Workspace B
2. The administrator creates multiple users on the Users page:
   • User 1
   • User 2
   • …
   • User n
3. The administrator creates a Developer role on the Roles page with permissions to create, edit, and delete inference endpoints.
4. On the Workspace Policies page, configure the corresponding permissions for different users:
   • Assign some users Workspace A with the Developer role.
   • Assign other users Workspace B with the Developer role.