Content
View differences
Updated by Eric Schubert 1 day ago
**As** a user \[enter role of user\]
**I want to** connect my user account to external services on a central page \[enter objective\]
**so that** I can use that connection page as a link from anywhere, where I can't see current content due to not being connected. \[enter desired result\]
**Acceptance criteria**
* In **Account settings** the user must be able to connect his user account to available, external services <br>
**Technical notes**
* <br>
**Permissions and providers.
visibility considerations**
* The user must only see external services, that are visible to them.
_To whom is this feature visible?_
* File storages must be assigned to projects the user has a membership for.
_When is it not visible?_
**Translation considerations**
* Wiki providers are global _Key terms and are always available.
**Technical notes** phrases in the key languages_
**Out of scope**
* We already have a menu entry called **Access tokens**, where we have a tab called **Client tokens**. This page shows already <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the "Disconnect" path. When introducing the "Connect" use case, we should probably combine those two use cases into a single page? changes._
**I want to** connect my user account to external services on a central page
**so that** I can use that connection page as a link from anywhere, where I can't see current content due to not being connected.
**Acceptance criteria**
* In **Account settings** the user must be able to connect his user account to available, external services
**Technical notes**
* <br>
**Permissions
**Translation considerations**
**Technical notes**
**Out of scope**
* We already have a menu entry called **Access tokens**, where we have a tab called **Client tokens**. This page shows already
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of