MCdesk personal access token
Create a personal access token (PAT) in MCdesk for your MCdesk connection in MCintelligentplus
Get a personal access token for MCdesk
Your organization connects MCdesk to MCintelligentplus with an endpoint, and every member authenticates with their own personal access token (PAT). The token identifies you to MCdesk, so the tools act as you — never as a coworker or a shared service account.
Before you start
- Ask your MCintelligentplus organization owner to publish MCdesk to your workspaces. It appears under User Settings → Apps once it is available.
- Sign in to MCdesk in a browser with the account you use for tickets.
Create the token in MCdesk
- Sign in to your MCdesk deployment (for example
https://mcdesk.example.com). - Open your avatar menu and choose Profile (个人资料).
- Switch to the Personal Token (私人令牌) tab.
- Click Create token (or the equivalent button in your MCdesk version).
- Name the token after where it will be used, for example
MCintelligentplus, so it is easy to recognize and revoke later. - Confirm the creation. MCdesk shows the token once — copy it immediately and keep it in a safe place.
MCdesk may show expiry or permission options. When they exist, choose the narrowest set that still lets you read and update the tickets you need, and a rotation period that matches your security policy.
Connect MCdesk in MCintelligentplus
- Open User Settings → Apps and choose MCdesk.
- Paste the token into the Personal access token (PAT) field.
- Click Test. The test signs in to MCdesk with the token and lists the tools it can reach; it does not create or change anything.
- When the test passes, click Connect.
The token is stored encrypted and sent to MCdesk as the X-API-Key header on every call. It follows you into every workspace where the organization enabled MCdesk.
Rotate or revoke a token
- Rotate: create a new token in MCdesk, open Apps → MCdesk in MCintelligentplus, click Replace, paste the new token, test and save. Then revoke the old token in MCdesk.
- Revoke (lost device, suspected leak): revoke the token in MCdesk first. MCintelligentplus calls start failing with an authentication error and the Apps card offers Reconnect; create a replacement token and paste it there.
Troubleshooting
| Symptom | What it means | Fix |
|---|---|---|
| Test reports an authentication error | The token is wrong, expired or revoked | Create a fresh token in MCdesk and paste it again |
| Test passes but finds zero tools | The token is valid but MCdesk exposes nothing to it | Ask the MCdesk administrator to check the token's permissions and tenant |
| Chat says authentication expired | The token was revoked or expired after connecting | Reconnect on Apps → MCdesk with a new token |
| No MCdesk card under Apps | The organization has not enabled MCdesk for your workspaces | Ask your organization owner to assign MCdesk to your workspace |
Never share a personal access token: each member needs their own, and MCdesk audits actions per token.