---
sidebar_position: 7
title: Custom integrations
sidebar_label: Custom integrations
description: Enterprise customers can have Myop adapted to their environment — single sign-on, custom roles, data residency, audit export to your SIEM, private networking, integrations with your own tools, and contractual service terms.
keywords: [myop custom integration, enterprise sso, saml, okta, azure ad, entra id, custom roles, rbac, data residency, siem export, ip allowlist, enterprise sla, security questionnaire]
---
# Custom integrations

Every enterprise runs on its own identity provider, its own security rules and its own tools. Rather than
ask you to fit around a fixed feature list, we adapt Myop to your environment. The items below are
**built for a customer when they need them**, scoped together with your team, and delivered as part of
your enterprise agreement.

## Identity and access

- **Single sign-on.** Sign in to Myop through your identity provider (SAML or OpenID Connect, for example
  Okta, Microsoft Entra ID or Google Workspace), so access follows your existing accounts and offboarding.
- **Custom roles and permissions.** Roles that match how your teams work, for example authors who can
  edit but not release, or release rights limited to specific environments or components.
- **User provisioning.** Add and remove people automatically from your directory.

## Data and infrastructure

- **Data residency.** Keep your data in the region your regulations require, or in a dedicated
  deployment.
- **Private networking.** Restrict access to your networks with IP allowlists or private connectivity.
- **On-premises and air-gapped.** All of Myop inside your own closed network.
  [Read more](/docs/enterprise/on-premises).
- **Your security policies.** Response headers and content security policies that match your standards.

## Visibility and compliance

- **Audit export.** Stream changes, releases and key usage to your SIEM or log platform.
- **Reporting.** Usage and change reports in the format your governance process expects.
- **Security reviews.** Answers to your security questionnaire and the architecture documentation your
  review needs.

## Your tools and workflows

- **Integrations with your systems.** Connect Myop to your CMS, campaign tools, ticketing or chat, for
  example to open a ticket when a release needs approval, or to post to a channel when production changes.
- **Approval workflows.** Require sign-off before a change reaches production.
- **Custom automation.** Extend the [management API](/docs/enterprise/automate-components) for the
  operations your teams repeat.

## Service terms

- **Service levels and support.** Agreed availability targets, response times and a named contact,
  written into your agreement.

## How it works

1. **Tell us what you need.** In a technical intro, we go through your requirements and your environment.
2. **We scope it together.** You get a short written plan: what we build, how it fits your setup, and when.
3. **We build and deliver it** for your organization, and it becomes part of your agreement.

Not on this list? Ask. [Book a technical intro](https://calendly.com/hadar-myop/myop-technical-intro).