<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=590913) </details> <!--IssueSummary end--> ## Why are we doing this work Currently, we display all secrets in the secrets manager. If the list of secrets becomes too long, we should consider adding pagination. We may need to check usage and determine how many secrets are being stored per group/project, and at what volume impacts performance. Ideally, this feature should be implemented alongside https://gitlab.com/gitlab-org/gitlab/-/work_items/470460+ since we will need search functionality to make the UX of pagination easier for users. ## Relevant links Related: https://gitlab.com/gitlab-org/gitlab/-/work_items/470460+ A similar discussion was brought up in: https://gitlab.com/gitlab-org/gitlab/-/issues/583210#note_3097318228 ## Implementation plan * [ ] Determine at what volume number of secrets displayed impacts performance and define ideal limit at which to begin paginating * [ ] Assess other areas of the product that use pagination and use them as reference when defining pagination limits/behavior * [ ] ## Verification steps