Microsoft 365
Organizational sign-in, supported user administration, group behavior, and calendar task blocking where enabled.
Connections
Know what each connection reads before enabling it.
Identity, calendars, notifications, and engineering work use different permissions and data directions. Availability depends on plan, tenant configuration, provider setup, and acceptance testing.
Documented paths
Identity and work events use explicit customer authorization.
Organizational accounts and tenant configuration determine availability. Personal Microsoft and Gmail accounts are outside the organizational SSO path.
Google Workspace
Organizational sign-in, supported workspace administration, group behavior, and calendar availability where enabled.
Slack
Selected notifications for task assignment, due dates, and completion.
Microsoft Entra user search
An administrator searches on demand, selects users, and adds only those users to Commandix. The picker requests basic profile fields rather than directory-wide status or group access.
Engineering work
Jira and GitLab remain deployment-gated until provider setup and acceptance checks pass.
The current product code supports explicit project mapping and inbound work synchronization. Production credentials and customer authorization control whether the path is available.
| Provider | Current technical path | Deployment gate |
|---|---|---|
| Jira Cloud | OAuth authorization, accessible site and project discovery, explicit project mapping, inbound issue sync, manual sync, and mapped-project webhooks | Company-owned Atlassian OAuth credentials, required scopes, callback verification, one-project sync test, and Help Center update. |
| GitLab.com | Read-only OAuth, accessible project discovery, explicit project mapping, inbound issue sync, manual sync, and configured webhooks | Company-owned GitLab OAuth credentials, callback verification, one-project sync test, and Help Center update. |
| GitLab Self-Managed | Per-instance OAuth credentials, HTTPS origin validation, explicit mapping, inbound sync, and configured webhooks | Reachable trusted TLS endpoint, exact private-host allowlist when required, provider credentials, and instance acceptance test. |
Data direction
Connection language should state what moves and what does not.
Current engineering-system work is inbound and explicitly mapped. Commandix does not require Jira API tokens, GitLab personal access tokens, SSH keys, deploy keys, or write-enabled issue scopes for this path.
DiscoverAuthorized projects
The authorizing user can expose only projects they already have permission to see.
MapExplicit selection
Link an external project, create a scoped Commandix project, or ignore it.
SyncInbound work
Mapped issues enter Commandix with external identity and links.
OperateMonitor and pause
Review sync runs, webhook status, connection state, and failures.
Need Jira, GitLab, or identity requirements in the rollout?
Send the provider, hosting model, intended projects, account ownership, security requirements, and required launch date.