**As** an API user
**I want to** have distinct resources per workspace type
**so that** I easily understand what each resource does

**Acceptance criteria**

* Add a GET workspace index end point

* Returns a mix of workpace types and offers to filter by those

* Each work space type becomes its own resource: "Project", "Program", "Portfolio"

* The workspace type is also visible in the url

* For each workspace type (project already has those)

* add show, create (+form), update Begin of the insertion(+form)

* MoveEnd of the insertion Begin of the deletion (+form),End of the deletion schema Begin of the insertionendpoint to `workspaces`

* Move auxiliaryEnd of the insertion endpoints Begin of the insertion(e.g. available assignees) to `workspaces`

* Keep existing `projects` scoped endpoints to not break the API.


End of the insertion Begin of the deletion


End of the deletion **Technical notes**

* <br>


**Permissions and visibility considerations**

* Creation requires the type specific global permissions added in <mention class="mention" data-id="65850" data-type="work_package" data-text="###65850">###65850</mention>

* Otherwise, permissions from within the workspace are used same as currently for project.


**Translation considerations**

* _Key terms and phrases in the key languages_&nbsp;


**Out of scope**

* <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._