Integrations

Pro and above

Integrations connect your Scopingly organization to the tools your team already uses. Each integration is configured per organization — one place, managed by your org admins — and the framework is designed so new providers slot in without changing how you configure them.

Supported integrations

Provider	What it does
JIRA	Push epics and user stories into your JIRA project, and ingest actuals back for calibration
Slack	Send outbound notifications to a channel

JIRA

The JIRA integration works in both directions from a single connection:

• Push out. Send generated epics and their user stories into JIRA as issues, so delivery breakdowns land where your team tracks work.
• Pull back. Ingest completed-work signal (actuals) from JIRA to feed calibration — so the estimates you committed learn from what the work actually took.

Slack

Connect a Slack channel to receive outbound notifications from Scopingly. A test action lets an admin confirm the channel is wired up correctly before relying on it.

Who can configure integrations

Integrations are managed by org admins. Configuring an integration — and running the Slack test — requires the integrations entitlement, which is included on Pro and above. See the feature matrix for what each plan unlocks.

Per-org, keyed by provider

Each organization configures each provider independently. Your JIRA and Slack settings are yours alone and never shared across organizations.

How credentials are handled

Integration credentials — a JIRA API token, a Slack webhook URL — are treated as secrets:

• Encrypted at rest. Credential fields are stored encrypted, not in plaintext.
• Masked on read. When an admin views an integration, secret fields are never handed back in the clear — you see only whether a value is set, not the value itself.
• Preserved on save. Saving an integration without re-entering a secret keeps the stored credential, so you can update non-secret settings without wiping the connection.

A Slack webhook is a credential

A Slack incoming-webhook URL is a bearer credential — anyone holding it can post to your channel. Scopingly stores it encrypted and never returns it to the browser. Treat it with the same care you'd give a password.

Related

• Epics & user stories — what gets pushed to JIRA.
• Calibration — what actuals ingestion feeds.
• Feature matrix — which plans include integrations.
• Roles & permissions — the org-admin role that manages them.