**As** a user
**I want to** have a clear understanding which access tokens are active, create new ones or delete them
**so that** I can control all my access tokens in a single page

## Note

This Begin of the insertionfeatureEnd of the insertion Begin of the deletion work packageEnd of the deletion is Begin of the insertionan MVPEnd of the insertion Begin of the deletion a work in progress in order to kick start the discussionEnd of the deletion about Begin of the deletion improving the Access tokens settings. Probably the scope ofEnd of the deletion this Begin of the insertionpage andEnd of the insertion Begin of the deletion changesEnd of the deletion will be Begin of the insertiongradually improved oberEnd of the insertion Begin of the deletion divided in other work packages in order to makeEnd of the deletion the Begin of the insertionfuture with more details and capabilities.End of the insertion Begin of the deletion implementation chunks feasible.End of the deletion

## **Acceptance criteria**

* The Access tokens page will now be divided Begin of the insertionin sections in this order:End of the insertion Begin of the deletion between:End of the deletion
1. **API**
2. **iCalendar**
3. Begin of the insertion**OAuth**End of the insertion Begin of the deletion **Storages**End of the deletion
4. **RSS**
* Each of this sections will have a description below.
* Begin of the insertionFor the moment only **iCalendar** and **OAuth** will be able toEnd of the insertion Begin of the deletion Each section mightEnd of the deletion have more than one Begin of the insertiontoken (once ##15339 is completed)End of the insertion Begin of the deletion token. They also can be empty with only the link or explanation how to add new tokens.End of the deletion
* Begin of the insertionIn the empty statusEnd of the insertion Begin of the deletion ForEnd of the deletion **API** and **RSS** an action below to add a Begin of the deletion newEnd of the deletion token. Below the **iCalendar** Begin of the insertionand **OAuth**End of the insertion an information text explains the user how calendar tokens works.
* Begin of the insertionWhen clicking on the link bellow **API** or **RSS** to generate a token a toast will appear with the API (current implementation).
* End of the insertion All the tokens can be deleted individually. A Begin of the insertiontoastEnd of the insertion Begin of the deletion confirmation messageEnd of the deletion will be displayed Begin of the insertiononceEnd of the insertion Begin of the deletion beforeEnd of the deletion the Begin of the insertiontokenEnd of the insertion Begin of the deletion actionEnd of the deletion is Begin of the insertiondeleted and the section will go back to the empty state_._End of the insertion Begin of the deletion performed _(to be designed)._End of the deletion
* The name of the **iCalendar** tokens Begin of the insertionwill containEnd of the insertion Begin of the deletion followEnd of the deletion the Begin of the insertionextra column to show the project where the calendar is located. The calendar name is the first column andEnd of the insertion Begin of the deletion structure: "Project - Calendar name". ThisEnd of the deletion should be a link that redirects to the calendar itself.
* The Begin of the insertion**iCalendar** tokens are the only ones that contain expiration dates for now.
* The **OAuth**End of the insertion Begin of the deletion **Storages**End of the deletion section contains Begin of the insertionallEnd of the insertion the OAuth Begin of the insertiontokens includingEnd of the insertion Begin of the deletion related to theEnd of the deletion active Begin of the insertionstorages. A second column also appearsEnd of the insertion Begin of the deletion storages with format "Storage name (Provider)". Bellow the **Storages** an information text explains the user howEnd of the deletion to Begin of the insertionindicate which is the application connected.End of the insertion Begin of the deletion add a new storageEnd of the deletion
* Begin of the insertionIn case the administrator of the instance has deactivated through admin settings either theEnd of the insertion Begin of the deletion _\[Work in progress\]_ Once a user creates a newEnd of the deletion **API** Begin of the insertionorEnd of the insertion Begin of the deletion token a modal opens and allowsEnd of the deletion the Begin of the insertion**iCalendar**End of the insertion Begin of the deletion user to give itEnd of the deletion a Begin of the insertionfix toast appears in the sectionEnd of the insertion Begin of the deletion nameEnd of the deletion and Begin of the insertionthe add link is removed.End of the insertion Begin of the deletion also specify which permissions this **API** token will contain.End of the deletion

## To be clarified together with the devs

* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion Divide the concept into feasible work packages and have a plan of implementation.
* [ ] RSS
* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion Do we need also options like the ones for creating an **API** token for the **RSS**?
* [ ] What is RSS is currently doing do we still need it
* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion Is there any of this tokens that has expire date? Do we need expire dates? If yes, we should be able to edit them.
* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion Is there any other action needed in the action column for any of the tokens?
* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion The texts below each token should be reviewed.

# Out of scope

* Implementing scopes for the API tokens to limit their Begin of the insertionpermissions (part of <mention class="mention" data-id="47735" data-type="work_package" data-text="#47735">#47735</mention>).End of the insertion Begin of the deletion permissions.End of the deletion
* Having more than one API Begin of the insertiontoken (part of <mention class="mention" data-id="47735" data-type="work_package" data-text="#47735">#47735</mention>).End of the insertion Begin of the deletion token.End of the deletion

## Visuals

<img class="op-uc-image op-uc-image_inline" Begin of the insertionsrc="/api/v3/attachments/55083/content"><imgEnd of the insertion Begin of the deletion src="/api/v3/attachments/54795/content"><imgEnd of the deletion class="op-uc-image op-uc-image_inline" Begin of the insertionsrc="/api/v3/attachments/55086/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55084/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55085/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55087/content">End of the insertion Begin of the deletion src="/api/v3/attachments/54019/content">End of the deletion

## Figma

https://www.figma.com/file/qivvu0fvo3EeIn9KlxuxJJ/Access-tokens?node-id=0-1