Content
View differences
Updated by Marc Alcobé 10 months ago
**As** a user \[enter role of user\]
**I want to** have access to multiple OpenProject apps for each custom instance \[enter objective\]
**so that** I can access the correct instance with the correct UI \[enter desired result\]
**Acceptance criteria**
* We build two separated flavoured apps for:
* OpenProject
* PMflexONE
* Each app have their respective colours, logos, and styles.
* Users can download both apps in a single device if required.
* _\[open\]_ In the PMflexONE application, the introduction of an `Instance URL` is not required for the login process, as it is always [`https://pmflex.one/`](https://pmflex.one/). Therefore, the login page has only a login button in it. <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br> _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have access to multiple OpenProject apps for each custom instance
**so that** I can access the correct instance with the correct UI
**Acceptance criteria**
* We build two separated flavoured apps for:
* OpenProject
* PMflexONE
* Each app have their respective colours, logos, and styles.
* Users can download both apps in a single device if required.
* _\[open\]_ In the PMflexONE application, the introduction of an `Instance URL` is not required for the login process, as it is always [`https://pmflex.one/`](https://pmflex.one/). Therefore, the login page has only a login button in it.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br>
* _When is it not visible?_
* _Key terms and phrases in the key languages_
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._