Plan the rollout

Before you connect anything, define the goals, owners, and signals that will show success.

  • Prioritize connectors: Start with the tools delivering the most context (e.g., GitHub, Jira, Slack) before expanding.
  • Document owners: Assign an admin, a compliance reviewer, and at least one manager that benefits immediately.
  • Secure scopes: Clarify the OAuth scopes or tokens needed, and store them in a vault before pasting them into Sizemotion.

Use the Integrations Hub

The Integrations Hub centralizes status, quick actions, and configuration links.

  • Status badges: Green indicates healthy syncs, amber flags a permission or token issue, and gray shows a disabled connector.
  • Quick actions: Launch overview, metrics, or config flows directly for each integration.
  • Health signals: Review last sync timestamps, rate limits, or webhook delivery failures before you troubleshoot.

Connect each integration

Follow these patterns for each connector:

  • GitHub: Create a personal access token with repo and admin:repo_hook scopes, copy the token, and paste it on /integration/github/config. Enable webhooks if you want real-time updates.
  • Jira: Generate an API token from https://id.atlassian.com/manage/api-tokens, enter the Atlassian domain, email, and token on /integration/jira/config, then select boards and projects.
  • Slack: Authorize Sizemotion inside Slack, grant channel/post access, and map teams to channels via /integration/manage/slack.
  • Bitbucket: Use an App Password with repo + pullrequest scopes and add the workspace on /integration/bitbucket. Register webhooks for push and pull events if needed.

Governance checklist

Keep your integrations secure and compliant:

  • Rotate credentials: Schedule token/app password rotation every 90 days or when a contributor leaves.
  • Audit logs: Review who enabled, disabled, or reconfigured connectors via the admin audit trail.
  • Least privilege: Grant only the smallest set of scopes necessary; avoid broad permissions unless required.
  • Data ownership: Clarify where synced data lives and who owns any derived insights (security, compliance, product).

Automate maintenance

  • Notification rules: Subscribe to alerts outside Sizemotion (Slack, email) when syncs fail or tokens expire.
  • Programmatic checks: Use the Incident API to create alerts when integrations report errors.
  • Documentation: Keep your internal playbook updated with URLs for config pages, tokens, and escalation contacts.

Next steps