**As a** project administrator
**I want to** create and manage sub-types scoped to my own project
**so that** I can tailor a type for my project without affecting other projects or needing an instance administrator.

## Background

Allowing types to only be managed globally is a hard requirement for many organizations, while other organizations see it as the absolute opposite, resulting in high administrator load for customizations.

The challenging part of this feature is **in-project visibility isolation**: a project's private sub-types must be invisible and unusable to every other project. At the same time, these project-specific sub-types need to be listed globally so they can be managed, and possibly promoted to global.

## Limitations

This feature only concerns the management of sub-types. It does not allow project administrators to create global types, nor does it allow to create new custom fields.

## Acceptance criteria

* With the Begin of the insertion`:manage_project_variants`End of the insertion Begin of the deletion `:manage_subtypes`End of the deletion project permission, I can create and manage Begin of the insertionvariantsEnd of the insertion Begin of the deletion sub-typesEnd of the deletion owned by my project

* A project-owned Begin of the insertionvariantEnd of the insertion Begin of the deletion sub-typeEnd of the deletion is visible and usable only within its owning project. Administrators of other projects cannot see it, select it, activate it, or link an aspect to it

* Instance administrators can see project-owned sub-types in global administration, with the owning project clearly indicated

* A project-owned Begin of the insertionvariantEnd of the insertion Begin of the deletion sub-typeEnd of the deletion can only be activated in its owning project

* A reuse source is always a global type

* A project-owned sub-type may link its aspects only to Begin of the insertion

* End of the insertion global types (such as its Begin of the insertionparent) 

* project-specific variants _in the same_ project

* End of the insertion Begin of the deletion parent) andEnd of the deletion can never be used as a reuse source by any other Begin of the insertionvariant, global or _other_ projects

End of the insertion Begin of the deletion type. 

End of the deletion * There is no cross-project linking of Begin of the insertionvariants,End of the insertion Begin of the deletion sub-types,End of the deletion even if both projects are visible to the same project administrator

* The names of project-owned sub-types are unique per project


## Permissions and visibility considerations

* **To whom is this feature visible?**

* Project members with Begin of the insertion`:manage_project_variants`End of the insertion Begin of the deletion `:manage_subtypes`End of the deletion (for their own project's sub-types)

* Global administrators

* **When is it not visible?**

* Feature flag turned off

* users without Begin of the insertion`:manage_project_variants`End of the insertion Begin of the deletion `:manage_subtypes`End of the deletion

* **a project-owned sub-type is never visible to any project other than its owner.**


## Translation considerations

All non-English wording is tentative and to be confirmed via Crowdin.

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">English</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">German (verify)</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">French (verify)</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Spanish (verify)</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Project sub-type</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Projekt-Untertyp</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Sous-type de projet</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Subtipo de proyecto</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Owned by {{project}}</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Gehört zu {{project}}</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Appartient à {{project}}</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Pertenece a {{project}}</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Only available in this project</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Nur in diesem Projekt verfügbar</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Disponible uniquement dans ce projet</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Disponible solo en este proyecto</p></td></tr></tbody></table></figure>

## Out of scope

* Promotion of a project-owned sub-type to global (TBC)

* Transferring ownership of a sub-type between projects.


## Resolved decisions

* **Cross-project linking.** Not allowed in any form. A reuse source is always a global type.

* A project-owned sub-type may link only to global types and may never be a source itself.

* A sub-type is therefore either limited to a single project or managed globally