modelscope / modelscope/ultron

Question: Support for Multi-Tenancy or Group-based Asset Isolation

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
180
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Hi Team,

Question:
Does Ultron currently support multi-tenancy or grouping?

Background & Scenario:
In our organization, we have different business units that require isolated management of assets—such as data, models, and prompts—under separate tenants or groups. Being able to cleanly separate assets for different contexts would greatly improve both the flexibility and security of our deployment.

If such functionality is not yet available, is it on the roadmap or planned in future versions?

Thank you for your clarification and any advice on how to approach this!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue names no files, tests, or entry points and asks whether multi-tenancy or group-based asset isolation exists or is planned. Start by checking the project's current asset-management documentation and implementation, then ask maintainers to define the supported scope; done requires a decided, actionable feature specification rather than a question.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.