To authorize team members to create GitHub issues via the
Wizard Browser Extension,
react to Telegram messages with an emoji, or copy chat history from Telegram
groups (both handled by the
Holdex Telegram Client),
edit
config/sales-team.json:
{
"telegramToGithub": {
"123456789": "alice-gh",
"987654321": "bob-gh"
},
"githubDefaultAssignee": "team-lead-gh",
"defaultGithubRepo": {
"production": { "org": "my-org", "repo": "default-repo" },
"development": { "org": "my-org-dev", "repo": "sandbox-repo" }
}
}
| Field | Purpose |
|---|---|
telegramToGithub |
Telegram ID to GitHub username. Keys = allow list, values = issue assignees. |
githubDefaultAssignee |
Fallback assignee when the mapped GitHub username is invalid. |
defaultGithubRepo |
Default org / repo for GitHub issues when a deal has no github_repo, for DMs, and when a create-issue request does not supply another org/repo. Uses the development entry when NODE_ENV=development, otherwise production. |
[!TIP] Adding a new team member only requires one edit here — this is the single source of truth for access control and issue assignee resolution.