Phase 1: 'Activation'

Claude for Enterprise org-wide technical configuration

Your technical foundation unlocks transformation. While your IT Lead handles the configuration, understanding this process ensures smooth coordination and rapid deployment. The steps below transform purchased licenses into a secure, ready-to-use AI platform.

The Configuration Journey

  1. Organization purchases Claude for Enterprise → Anthropic creates your instance
    • Note: the person who purchases Claude will be the Primary Owner
  2. Primary Owner receives setup email → (21-day acceptance window—act quickly!)
  3. Primary Owner configures authentication → (Additional information on how to in Primary Owner Checklist below)
  4. Organization provisions users → Decide how and who gets access to Claude! 

Your data stays yours. Anthropic never trains models on Claude for Enterprise data - your business intelligence remains completely confidential.

Primary Owner Checklist

Security and Access 

  1. Complete the domain verification process (required to use SSO)
  2. Configure Single Sign-On (SSO) for secure authentication
    1. Setting Up SSO on the Enterprise Plan 
    2. Important Considerations Before Enabling SSO
    3. Test SSO 
  3. Decide how you will provision accounts for your end users 
    1. User provisioning and management
    2. How to enable SCIM 
  4. [Optional] Audit Claude accounts associated with your domain. This will help you identify users who have been using their work emails for non-Enterprise accounts and define a path forward 
    1. See PDF attached to this lesson for more guidance.
  5. [Optional] Set custom data retention policies for chats and projects

User Roles and Permissions 

  1. Configure user Roles and Permissions; assign seat types
    1. Roles & Permissions 
    2. For Premium Seats, you can set tiers at user level in the ‘Members’ tab of your Settings.
    3. For Extra Usage, you can assign usage limit controls to users on 
  2. Enable Integrations for your organization
    1. Setting Up Integrations on Claude.ai 
  3. [Optional] Manage team access to desktop extensions for Claude desktop use via enabling/disabling desktop extensions. 
    1. Additionally, upload custom desktop extensions to make them available to your team for one-click install.
  4. Set project sharing and collaboration policies
    1. Project Visibility and Sharing
    2. How can I disable public projects? 
  5. Enforce SSO 

Important considerations:

  • Provisioning and notification of end users
    • SCIM or JIT provisioning doesn't notify users, letting you set up early without impacting your communications timeline—we recommend doing this first. Manual provisioning sends emails with a 21-day acceptance window 
    • How do I add a member to my team? 
  • Usage limits and deciding when to give more usage

Once you have completed these steps, your end users will be able to login safely and securely to your organization’s Claude.ai instance. Next, we recommend that you work with your Project Team to plan your change management strategy in preparation for launch.