> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise plan

> SSO, SCIM, IP restrictions, audit logs, data retention, and dedicated cloud. See what the Enterprise plan offers for security and organization management.

export const PlanGateCard = ({plan, page, lang = "ko", children}) => {
  const BADGE = {
    pro: {
      ko: "Pro+",
      en: "Pro+",
      ja: "Pro+"
    },
    team: {
      ko: "팀 플랜",
      en: "Team Plan",
      ja: "チームプラン"
    },
    enterprise: {
      ko: "엔터프라이즈",
      en: "Enterprise",
      ja: "エンタープライズ"
    }
  };
  const COPY = {
    pro: {
      ko: {
        lead: "이 기능은 Pro 플랜 이상에 포함되어 있어요.",
        tail: "지금 쓰는 워크스페이스에서 바로 업그레이드할 수 있어요.",
        cta: "플랜 업그레이드하기"
      },
      en: {
        lead: "This feature is included in Pro plans and above.",
        tail: "You can upgrade right from your workspace.",
        cta: "Upgrade your plan"
      },
      ja: {
        lead: "この機能はProプラン以上でご利用いただけます。",
        tail: "ワークスペースからすぐにアップグレードできます。",
        cta: "プランをアップグレード"
      }
    },
    team: {
      ko: {
        lead: "이 기능은 함께 쓰는 워크스페이스에서 진가가 나와요.",
        tail: "팀원을 초대하면 바로 시작할 수 있어요.",
        cta: "팀원 초대하기"
      },
      en: {
        lead: "This feature shines in a shared workspace.",
        tail: "Invite your teammates to get started.",
        cta: "Invite teammates"
      },
      ja: {
        lead: "この機能はチームで使うワークスペースで真価を発揮します。",
        tail: "メンバーを招待してすぐに始められます。",
        cta: "メンバーを招待"
      }
    },
    enterprise: {
      ko: {
        lead: "이 기능은 엔터프라이즈 플랜에서 제공돼요.",
        tail: "조직에 필요한 보안 구성을 영업팀이 함께 설계해 드려요.",
        cta: "도입 문의하기"
      },
      en: {
        lead: "This feature is available on the Enterprise plan.",
        tail: "Our sales team will help design the security setup your organization needs.",
        cta: "Contact sales"
      },
      ja: {
        lead: "この機能はエンタープライズプランでご利用いただけます。",
        tail: "組織に必要なセキュリティ構成を営業チームがご支援します。",
        cta: "導入のお問い合わせ"
      }
    }
  };
  const HREF = {
    pro: "https://tiro.ooo/" + lang + "/n?utm_source=docs&utm_medium=plan_callout&utm_campaign=plan_upsell_pro&utm_content=" + page + "#settings/plans",
    team: "https://tiro.ooo/" + lang + "/n?utm_source=docs&utm_medium=plan_callout&utm_campaign=plan_upsell_team&utm_content=" + page + "#settings/plans",
    enterprise: "https://tiro.ax/" + lang + "/contact?utm_source=docs&utm_medium=plan_callout&utm_campaign=plan_upsell_enterprise&utm_content=" + page
  };
  const copy = COPY[plan][lang];
  return <div className="plan-gate-card">
      <div className="plan-gate-card-text">
        <span className="plan-gate-card-title">
          {({
    pro: "Pro Plan",
    team: "Team Plan",
    enterprise: "Enterprise Plan"
  })[plan]}
        </span>
        <p>
          {copy.lead} {children} {copy.tail}
        </p>
      </div>
      <a className="plan-gate-card-button" href={HREF[plan]}>
        {copy.cta}
        <svg width="15" height="15" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d="M5 12h14" /><path d="m12 5 7 7-7 7" /></svg>
      </a>
    </div>;
};

export const PlanBadge = ({plan, lang = "ko"}) => <span className="plan-badge">
    {({
  pro: {
    ko: "Pro+",
    en: "Pro+",
    ja: "Pro+"
  },
  team: {
    ko: "팀 플랜",
    en: "Team Plan",
    ja: "チームプラン"
  },
  enterprise: {
    ko: "엔터프라이즈",
    en: "Enterprise",
    ja: "エンタープライズ"
  }
})[plan][lang]}
  </span>;

<PlanBadge lang="en" plan="enterprise" /> This is an Enterprise plan feature.

The Enterprise plan adds the **security, organization management, and integrations** your company needs on top of everything in the Team plan. You can unify login with your corporate identity provider, govern several workspaces from one place, and connect Tiro to your internal systems. See what's possible at a glance below, then follow each link for the details.

Enterprise is a consultation-based plan. We review your organization's requirements and design the setup with you, so [contact us](https://tiro.ax/en/contact?utm_source=docs\&utm_medium=cta\&utm_campaign=enterprise_inquiry\&utm_content=guide-workspace-enterprise) when you see a capability you need.

<Note>
  SSO and SCIM are separate options, and the rollout schedule and scope for SCIM are agreed separately. Only the options selected in your contract are enabled, and each appears as a separate line item on your quote.
</Note>

## How do I unify login with corporate accounts (SSO)?

SAML 2.0 single sign-on connects Tiro to your corporate identity system. Connect an IdP like Okta, Azure AD (Microsoft Entra ID), or Google Workspace, and your people sign in to Tiro with one company account.

* **SSO (SAML 2.0)**: Sign in with a company account, with access kept in sync with your IdP policies. You can also enforce SSO-only login and block other sign-in methods.

For setup and closed-network support, see [Organization security settings](/en/guide/privacy/enterprise-security).

## How do I automate joiner and leaver account management with SCIM?

SCIM provisioning is an option whose rollout schedule and scope are agreed separately from SSO. It is used to sync user information between your IdP and Tiro and automate account operations such as creating accounts for joiners and revoking access for leavers.

The handling of account and note data is agreed during rollout based on your organization's IdP and operating policies. SSO alone is enough to unify login.

## Control access

Restrict who connects, from where, and on which device, to match your organization's policies.

* **MFA (multi-factor authentication)**: Strengthen account security with OTPs, authenticator apps, or hardware keys.
* **IP allowlist**: Allow access only from approved IP ranges, so only office or VPN traffic gets through.
* **Session and device controls**: Set session lifetime, concurrent session limits, and device registration limits as policy.
* **Mobile screen capture protection**: Block screenshots inside the mobile app.

## Protect sharing and personal information

Keep notes from leaving your organization by governing share scope and personal data with policy.

* **External sharing controls**: Open sharing only to approved company domains, and set caps on share scope and link lifetime. Revoke active links from one place. For details, see [Share link security](/en/guide/sharing/link-security).
* **Allowed invite domains**: Set separate allowed email domains for inviting workspace members and note collaborators. This is distinct from the domain policy for share links.
* **PII masking**: Automatically hide sensitive identifiers like national IDs, phone numbers, and account numbers in new notes. This option fits environments where personal data comes up often, such as call centers.

## Manage multiple workspaces in one place

Govern policy from one place even when your organization is split across several workspaces.

* **Usage dashboard**: See usage across the organization and by team at a glance.
* **Bulk policy**: Apply settings like data retention windows, external sharing domains, and session lifetime across the whole organization. You don't have to touch each workspace one by one.
* **Organization workspaces only**: Restrict members from creating new notes or moving notes into workspaces outside the organization. Existing notes in those workspaces remain viewable.
* **Preserve departing members' notes**: An option to keep notes in an organization archive workspace when a member leaves.

For roles and permissions within the organization, see [Roles and permissions](/en/guide/workspace/roles).

## Handle data to meet your compliance needs

Configure how data is stored, retained, and deleted to match your organization's compliance requirements.

* **Data retention policy**: Set retention windows by domain (for example, 90, 180, or 365 days), with automatic deletion when the window closes.
* **Paragraph audio replay period**: Set how long members can replay audio for each paragraph, or restrict replay through organization policy. This is separate from note retention.
* **Complete deletion and erasure receipts**: On account closure or a deletion request, data is removed irreversibly, and the request through completion is logged as a JSON or PDF receipt.
* **Audit logs**: Keep user and admin activity logs (with configurable retention), and export them as a CSV file from the screen. If your company runs a SIEM, you can also receive the same events in real time as JSON over an HTTPS webhook.
* **Access logs**: Request a CSV of organization access records for a selected period. This option is enabled separately from audit logs.
* **Vendor routing allowlist**: Choose which LLM and STT vendors are available, and configure rules like Korea-only routing to meet data sovereignty requirements.
* **Dedicated cloud**: Discuss a physically isolated, dedicated environment and additional security options.

Baseline data storage and security (storage in the AWS Seoul region, encryption at rest, no use of your data for AI training) are the same on every plan. See [Privacy and security](/en/guide/privacy/overview).

## Connect to your internal systems

Connect Tiro to your internal workflows with integration options.

* **Dedicated API and webhooks**: Pull note, transcript, and summary data into your internal systems, or build a custom integration that fits your organization's requirements.
* **Shared login domain**: Run login through a shared corporate domain.

To build an integration yourself, see [API overview](/en/developers/fundamentals/api-overview), [MCP overview](/en/developers/mcp/mcp-overview), and [Webhooks overview](/en/developers/webhooks/webhooks-overview).

## Onboarding and support

* **Custom onboarding and a hotline**: Get custom onboarding sessions through a dedicated hotline, with fast responses to security-related requests.
* **Service level agreement (SLA)**: A monthly 99.9% availability target, with service credits if it isn't met.

## Frequently asked questions

### How do I start on the Enterprise plan?

Enterprise isn't a plan you subscribe to with a card. It's consultation-based. Reach out through the [contact form](https://tiro.ax/en/contact?utm_source=docs\&utm_medium=cta\&utm_campaign=enterprise_inquiry\&utm_content=guide-workspace-enterprise) or [partners@theplato.io](mailto:partners@theplato.io), and our sales team reviews your organization's security and operations requirements and designs the setup with you.

### How is the Team plan different from the Enterprise plan?

The Team plan is a self-service plan you subscribe to directly with a card, while Enterprise is a consultation-based plan for organizations that need SSO, security policies, and custom integrations. For a plan comparison, see [Tiro plans](/en/guide/workspace/plans).

### Do I have to turn on every security feature?

No. You can pick only the features you need. During onboarding, we review your organization's requirements and configure only the options you want.

### Can I get security review materials?

Yes. Tiro holds ISO/IEC 27001:2022 certification and has completed both SOC 2 Type 1 and Type 2 audits. Security review materials such as audit reports, data locations, and the subprocessor list are provided after an NDA. Check the current certification status in the [Trust Center](https://trust.tiro.ooo), or contact our sales team.

<PlanGateCard lang="en" plan="enterprise" page="guide-workspace-enterprise" />

***

**Related pages**: [Organization security settings](/en/guide/privacy/enterprise-security) · [Share link security](/en/guide/sharing/link-security) · [Tiro plans](/en/guide/workspace/plans) · [Privacy and security](/en/guide/privacy/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.