Related to
Web-Backend (APIs), Web-Frontend (what users interact with)
Impact
better user experience
Missing Feature
Currently, API tokens in Semaphore have no identifying label. When a user creates multiple tokens for different purposes (CI pipelines, scripts, integrations), there's no way to tell them apart in the UI — they all appear as truncated token IDs. This makes it difficult to manage tokens, especially when deciding which one to revoke or when dealing with a large number of them. I would need to maintain a separate document (which maps the keys to each integration i have configured
Implementation
I have logged a PR for this already please look at PR #3788
Design
refer to PR #3788
Related to
Web-Backend (APIs), Web-Frontend (what users interact with)
Impact
better user experience
Missing Feature
Currently, API tokens in Semaphore have no identifying label. When a user creates multiple tokens for different purposes (CI pipelines, scripts, integrations), there's no way to tell them apart in the UI — they all appear as truncated token IDs. This makes it difficult to manage tokens, especially when deciding which one to revoke or when dealing with a large number of them. I would need to maintain a separate document (which maps the keys to each integration i have configured
Implementation
I have logged a PR for this already please look at PR #3788
Design
refer to PR #3788