General Settings — API Tokens

 TraCorp LMS Quick Reference Guide (QRG)

Audience: Main Admin

Overview

This QRG explains the API Tokens section in General Administration. API Tokens allows Main Admins to manage the credentials used by external tools that connect to the LMS API, including generating, rotating, and deactivating tokens, and deactivating the legacy Global Client Key, shown in the grid as lms_user.

Enabled Permissions Required to Complete the Following Steps

• General Settings > General Administration

Note: Sub Admin and User Group Admin do not have access to these settings.

Generate a New Token

1. From Admin Navigation, click General Settings.
2. Click General Administration.
3. Scroll to the API Tokens section.
4. Click Generate New Token.
5. Enter a Label describing the token’s purpose (e.g., “Jane’s Claude Desktop”).
6. Select the Associated User from the list (Sub Admins and User Group Admins only).
7. Click Generate.
8. Copy the token value shown — it will not be displayed again.
9. Click Close.

Rotate a Named Token

1. From Admin Navigation, click General Settings.
2. Click General Administration.
3. Scroll to the API Tokens section.
4. Locate the token in the grid.
5. Click Rotate next to the token.
6. Click Continue to confirm. This immediately invalidates the current token value for any connected tool.
7. Copy the new token value shown — it will not be displayed again.
8. Click Close.

Deactivate a Named Token

1. From Admin Navigation, click General Settings.
2. Click General Administration.
3. Scroll to the API Tokens section.
4. Locate the token in the grid.
5. Click Deactivate next to the token.
6. Click Continue to confirm.

Note: The token’s label and history remain visible in the grid with an Inactive status.

Deactivate the Global Client Key (lms_user)

1. From Admin Navigation, click General Settings.
2. Click General Administration.
3. Scroll to the API Tokens section.
4. Click Deactivate next to the lms_user row — this is the Global Client Key. The grid identifies it by this Client ID; there is no separate “Global Client Key” label displayed.
5. Click Continue to confirm.

Note: Deactivating lms_user immediately stops any tool still using it, including MCP clients and direct REST API integrations. Confirm all integrations have been moved to named tokens first — this action cannot be undone from this interface.

Best Practices

Generate a separate named token for each person or tool connecting to the LMS API, including AI tools such as Claude, instead of sharing one credential. Named tokens can be rotated or deactivated individually without affecting other integrations. Once all existing integrations are using named tokens, deactivate the Global Client Key (lms_user in the grid) to remove the shared credential.