Claude Design lets your team create on-brand designs, prototypes, presentations, and interactive microsites through conversation with Claude.
Claude Design is available in beta to Pro, Max, Team, and Enterprise plans. This capability is default off for Enterprise plans.
Claude Design works best when a design system is set up for your organization first. This ensures every project your team creates stays true to your brand, typography, color palette, and component patterns. This guide walks you through enabling Claude Design, setting up the right foundation, and rolling it out to your team.
Enable Claude Design for your organization
Claude Design is available via a toggle in organization settings, and can be controlled using custom roles.
Before you enable broad access, read through the rollout approach below. Turning on Claude Design without a design system in place means your team will get functional but generic output.
Team and Enterprise plan admins can enable this organization-wide by following these steps:
Find the Claude Design toggle under Anthropic Labs and switch it on.
The design system: why it comes first
The single most important thing you can do before rolling out Claude Design is have an experienced designer set up your organization’s design system. Once in place, every project your team creates automatically reflects your brand.
This means your rollout has a natural sequence: design system setup first, then broader access.
Who should set up the design system
For best results, we recommend pulling in designers across both brand and product design. Together they can ensure the design system covers both brand identity and product UI patterns.
What they’ll do
Create your organization in Claude Design (see Set up your design system in Claude Design).
Complete the onboarding flow.
Upload brand assets (codebases, slide decks, or other design references).
Validate that Claude generates designs consistent with your brand.
Any member with Claude Design access can create and edit design systems. On the Enterprise plan, you can restrict who can publish design systems, set the organization default, and delete design systems.
Restrict who can manage design systems
The Claude Design Admin permission is available on the Enterprise plan through custom roles.
By default, any member with access to Claude Design can publish a design system, set the organization default, and delete design systems. The Claude Design Admin permission lets you reserve these actions for specific members, giving your organization a single source of truth for its design systems.
What the permission controls
Members with the permission set to "Can manage" can:
Publish a design system: Make it available across your organization so anyone can attach it to a project.
Set the organization default: Choose the design system new projects use automatically.
Delete a design system: Permanently remove it from your organization.
Everyone else can still create, edit, and use any published design system. If a member without the permission tries to publish, set the default, or delete, they'll see a note directing them to contact their administrator.
Note: If you don't assign this permission to anyone, nothing changes. All members keep the same access to design systems as before.
Grant the permission
You'll need Owner access to configure roles.
Go to Organization settings > Roles and create or edit a custom role.
In the Permissions tab, find Claude Design Admin under In-app admin and set it to Can manage.
Assign the role to a group. Members of that group inherit the permission.
Set each member's role to Custom roles.
Permissions are additive. A member in multiple groups gets the union of what those groups' roles grant. Learn more about managing custom roles on Enterprise plans.
Verify access
Permission changes can take up to 15 minutes to apply, and members may need to refresh their browser. There are two ways to confirm:
Ask the member to check. In admin settings, they'll see only the sections their permissions cover.
Review as an Owner. Check the member's groups on the Members page, then review those groups' roles on the Roles page.
Recommended rollout phases
A phased rollout lets you validate your design system and build internal expertise before broad adoption. You can control access to Claude Design in accordance with each rollout phase using custom roles.
Phase 1: Design system setup
Who: 2–4 trusted designers and design leads across brand and product design.
Goal: Create and validate your organization’s design system, including product and slide deck templates everyone can use as a starting point.
Checkpoint: Review generated output for brand consistency before proceeding.
Phase 2: Design team onboarding
Who: Full design team.
Goal: Build familiarity with Claude Design; stress-test the design system across real projects.
Checkpoint: Gather feedback on design quality and refine the design system if needed.
Phase 3: Product and UX onboarding
Who: Product managers, UX researchers, and adjacent functions.
Goal: Enable faster prototyping and design collaboration beyond the design team.
Checkpoint: Observe usage throughout the organization and gather feedback on usability.
Phase 4: Broader organization
Who: Entire organization or specific departments.
Goal: Make design creation available widely while maintaining brand consistency.
Checkpoint: Observe usage throughout the organization and gather feedback on usability.
Rollout tips
Announce each phase clearly so people know when their turn is coming.
Consider running a short training session or office hours during early phases.
Establish a feedback channel for design system improvements.
Share examples of creative uses of Claude Design internally to help foster creativity.
What your team can do with Claude Design
Once set up, your team can use Claude Design to:
Create prototypes and mockups: Describe a UI and get a working interactive prototype.
Build presentations and slide decks: Generate on-brand decks through conversation, presentable as HTML, PDF, and PPTX.
Design microsites and landing pages: Create polished single-page sites.
Iterate with inline comments: Annotate designs directly on the canvas and ask Claude to implement changes.
Hand off to engineering: Export design intent for use with Claude Code or your existing development workflow.
We have more tutorials available here:
Monitor usage
Claude Design doesn’t support audit logs or usage tracking yet.
We recommend tracking adoption qualitatively during your rollout—check in with each group as they onboard, collect feedback, and sample a few projects periodically to assess design system compliance.
Data handling and privacy
When your team uses Claude Design, they may upload design assets, brand guidelines, screenshots, and other materials. Understanding how these are handled is important for organizations with data governance requirements.
Uploaded assets are stored persistently, and fall under the same data retention and deletion policies as other Anthropic enterprise products.
Claude Design doesn’t currently support data residency requirements.
Preview sandbox isolation
Claude Design project previews run inside a sandboxed iframe on a separate content domain that Anthropic operates. These sandboxed iframes help each project preview stay in its own space, separate from others. The code in a preview can't reach your Claude account, your login, or the editor.
Access to a preview is controlled by signed tokens—short-lived passes that prove someone's allowed in. Claude re-checks these tokens against your sharing permissions every time someone opens the preview, so when you remove someone's access, they're locked out right away.
Third-party platform availability
Claude Design is currently available only through the web interface at claude.ai/design.
If your organization requires Claude Design through your existing cloud provider agreements, reach out to your Anthropic contact or our Sales team.
Usage and billing
Claude Design usage counts toward each member's existing usage limits, shared with chat, Claude Code, and Cowork. There's no separate Claude Design allowance to provision or manage.
Team and seat-based Enterprise plans: Claude Design draws from each member's seat usage limits, including both session and weekly limits. Admins can purchase usage credits for members who need more capacity.
Usage-based Enterprise plans: Claude Design usage bills from your organization's consumption at standard API rates, like every other surface. Organization, group, and per-user spend limits apply.
Frequently asked questions
Do all team members need to upload brand assets?
No. Once a designer sets up your organization’s design system, all projects created within that organization automatically use it. Team members just start creating.
Can we have multiple design systems for different brands or sub-teams?
Yes. Organizations can have multiple design systems.
What happens if someone starts using Claude Design before the design system is set up?
They’ll get functional designs, but the designs won’t reflect your brand. We strongly recommend completing design system setup first for the best team experience.
Who can publish, set the default, or delete design systems?
If you haven't assigned the Claude Design Admin permission to anyone, any member with Claude Design access can take these actions. On the Enterprise plan, you can reserve these actions for specific members. See Restrict who can manage design systems above.
Can I restrict Claude Design to specific departments?
Yes. Use the RBAC controls to grant access to specific groups or departments rather than enabling it org-wide.
How many users can we onboard at once?
There are no strict limits, but we recommend the phased approach outlined above to ensure quality and successful adoption across your organization.
Can we export or archive generated designs?
Claude Design currently supports export to HTML bundles, PPTX, PDF, and hand-off to Claude Code or the following partners: Adobe, Base44, Canva, Gamma, Lovable, Miro, Replit, Vercel, or Wix. Reach out to your Anthropic Contact or our Sales team if there’s a specific format or destination you need.