Use Cases

This section introduces 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 or individual developers who only need one administrator to handle all operations. In this case, use the initial administrator account provided by Neutree.

Permission Separation

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

• Administrator: Global administrator permissions, responsible for overall platform management and maintenance.
• Developer: Specific workspace endpoint operation permissions, responsible for model deployment and inference service management.
• Auditor: Global read-only permissions, responsible for monitoring and auditing platform activities without modification privileges.

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:

   • “Developer” role, assigned permissions to create, edit, and delete endpoints.
   • “Auditor” role, assigned only view permissions for various modules.

3. Configure appropriate permissions for different users on the Workspace Policies page:

   • 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 requiring independent AI services for different teams, departments, or external customers while ensuring data isolation and resource security. You can implement multi-tenant isolation through workspaces, with each tenant having independent resource and model spaces to ensure business operations don’t interfere with each other and data remains secure and controllable.

• Administrator: Has global administrator permissions, responsible for building platform infrastructure and multi-tenant architecture.
• Tenant A Users: Only have specific operation permissions within Workspace A.
• Tenant B Users: Only have specific operation permissions 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, assigned permissions to create, edit, and delete endpoints.

4. Configure appropriate permissions for different users on the Workspace Policies page:

   • Assign some users to Workspace A with the “Developer” role.
   • Assign other users to Workspace B with the “Developer” role.