Profile
Profile contains settings owned by the signed-in user rather than by a workspace or installation administrator.
General profile
The General tab controls the display name shown in ownership, assignment, comments, and activity views.
The account email is supplied by the configured identity provider and cannot be changed in Polygent. Correct an email or sign-in identity at the identity provider, then sign in with the intended account.
TFS tokens
The TFS Tokens tab stores a personal Azure DevOps or TFS personal access token for a specific workspace.
Use a personal token when Git or pull-request operations should run under the user's identity instead of a shared workspace credential.
- Create a token in Azure DevOps or TFS with only the repository and work-item scopes required by the workspace integration.
- Open Profile → TFS Tokens.
- Select the workspace and save the token.
- Test the related ticket-sync or pull-request operation.
- Rotate the token before expiry and remove it when access is no longer needed.
Tokens are workspace-scoped, protected at rest, and are not displayed back to other workspace members. They remain external credentials: apply organization expiry policy, avoid broad scopes, and revoke them at the provider when a user leaves or a token may be exposed.
See Ticket Sync for workspace integration behavior.
Notification preferences
The Notifications tab controls whether this browser can display native notifications for new inbox items.
Browser notifications are off by default and require both the Profile setting and browser/operating-system permission. They require an open, signed-in Polygent tab and may expose notification text on the desktop or lock screen. After enabling them, select Send test notification to verify local delivery. See Notifications & My Work.
Devices
The Devices tab lists active signed-in devices when the installed license enables multiple active sessions.
Each row identifies the browser or user agent and recent use. The current device is marked separately. Select Revoke to invalidate another device's refresh session; revocation takes effect when that device next refreshes authentication. Revoke unknown, lost, or shared devices immediately.
Administrators can manage user sessions from the Users area. Device revocation does not revoke identity-provider sessions, personal access tokens, or host API keys; revoke those separately at their source.
Security response
Profile controls are part of account containment, not a replacement for identity-provider security.
If account access may be compromised:
- Revoke unfamiliar devices in Profile or ask an administrator to revoke them.
- Change or reset credentials and revoke sessions at the identity provider.
- Revoke and replace personal Azure DevOps/TFS tokens.
- Review workspace membership, roles, ticket activity, and system logs.
- Notify the administrator if repository or model credentials may also be exposed.
Troubleshooting
Profile failures usually come from identity-provider ownership, license features, browser permissions, or external-token scope.
| Symptom | Resolution |
|---|---|
| Email cannot be edited | Update it at the identity provider; Polygent treats the provider identity as authoritative. |
| Devices tab is absent | Confirm the license enables multiple active sessions. The current login remains usable without the tab. |
| Revoked device still appears active | Wait for its next authentication refresh; revoke the upstream identity-provider session for immediate broader containment. |
| Browser alerts do not appear | Enable the Profile setting, grant browser and OS permission, keep a signed-in tab open, select Send test notification, and test with the tab hidden. |
| Personal TFS token fails | Verify token expiry, organization, workspace selection, scopes, repository access, and network reachability. Replace the saved token after rotation. |
| Workspace is missing from token management | Confirm the user is a member of that workspace. |