LingoHub provides flexible API key management to connect third-party services and automated tools securely. Learn about the available API key types, management modes, and status tracking.
API key scopes
When creating an API key, you can assign one of three distinct scopes depending on the required level of access:
Workspace API keys: Provide access across all workspace-level settings, resources, and projects.
Project API keys: Restrict access exclusively to a specific project. These can also be viewed and managed directly within the project settings.
User API keys: Tied to an individual team member. Self-managed API keys (see explanation below) automatically inherit the permissions assigned to that specific user account. User API keys created by an admin (admin-managed keys, see explanation below) can have permissions different from the user.
Management modes: Self-managed vs. Admin-managed
Workspace API keys operate under two distinct management modes:
Self-managed keys: Created and managed by individual team members. These keys inherit the user's current permissions automatically.
Admin-managed keys: Created and controlled by workspace admins. Admins can explicitly define granular permissions for each key.
💬 Please note: Admins can choose to enable or disable self-managed API keys for the entire workspace at any time.
Inactive keys and transparency
To maintain security and auditability, inactive API keys remain visible in the API keys overview along with the exact reason for deactivation:
Key expiration
Member removal from the workspace
Project deletion
Manual revocation
Self-managed API key feature disabled by an Admin
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.