### Problem to solve While [improving the call-to-action for expired tokens](https://gitlab.com/gitlab-org/gitlab/-/issues/222734/), the idea was proposed to simplify the process of "[renewing](https://gitlab.com/gitlab-org/gitlab/-/issues/222734#note_401928733)" a token. If a user has a token that expired, they must first revoke the token and create a new one with the same configuration. ### Intended users Any user that does not have Personal Access Tokens automatically revoked when they expire. ### User experience goal Understand what the options are for managing a PAT that has expired (or will soon expired) ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> Use dropdown to create menu of options - Revoke (Same behavior) - Rotate (regenerate a new token with the same `scope` and `expiration period` without having to input all of that again)  ### What does success look like, and how can we measure that? - Reduction in time for tokens staying in an expired state ### Links / references <!-- Label reminders - you should have one of each of the following labels if you can figure out the correct ones --> - [Support for the value of this feature](https://gitlab.com/gitlab-org/gitlab/-/issues/222734#note_404762535)