Enhancing API Token Management for Targeted Access Control
Alireza Barkhordari
I have a suggestion for improving the app's API token system. Currently, only users with the "Manage API Tokens" permission can create API tokens. However, in some situations, as a product owner, I may need to provide an API token to another team in the company that only requires read access to the records.
To accomplish this right now, I have to create a role with limited access (no edit permission) for that team and also give them the "Manage API Tokens" permission. This allows them to create a token for themselves, but it comes with a problem. By giving them "Manage API Tokens" permission, they now have access to all API tokens, which defeats the purpose of restricting their access.
My feature request is to enhance the API token management in a way that allows me, as the product owner, to provide specific teams with read-only access to records by creating API tokens for them directly, without having to grant them "Manage API Tokens" permission. This would ensure better security and prevent giving unnecessary access to all API tokens.
J
Joe McCann
100 pct needed. A user (or maybe just the org owner?) ought to be able to generate API keys that are assigned arbitrary permissions, expiration, group membership, whatever. The api keys shouldn't consume a user slot on their orgnisation's plan. Please.
P
Philip Harvey ( US )
Each token should be able to be scoped and assigned permissions.