Admin Setup

Last verified: 14 April 2026 | Applies to: Team, Enterprise

In 30 seconds

Setting up Claude for your organisation involves configuring seats, provisioning plugins and skills, connecting shared tools, and establishing usage guidelines. This guide covers the admin setup from first login to a production-ready deployment.

What it does

Seat management

Team plans have two seat types:

• Standard ($25/mo per seat): 1.25x Pro usage. Chat, Cowork, plugins, connectors, and Claude Code.
• Premium ($150/mo per seat, or $100/mo with annual billing): 6.25x Pro usage. Everything in Standard with a significantly higher usage allowance.

Assign seat types based on usage intensity:

• Most team members → Standard
• Power users who consistently hit Standard usage limits → Premium
• Start Standard, upgrade as needed based on actual usage

Enterprise plans are self-serve, no sales call required. Minimum 20 seats, single seat type, annual billing. Configure directly from the Enterprise signup page.

Plugin provisioning

Admins can provision plugins org-wide:

1. Go to your admin dashboard
2. Select plugins to install for the organisation
3. Set default state: enabled or disabled for new users
4. Users can toggle plugins on/off within the admin’s allowed set

Recommended baseline: Provision the Productivity plugin for all users (enabled by default). Add function-specific plugins, including department-specific options like PE modelling, HR, design, and operations, as optional based on team needs.

Enterprise plans also support private plugin marketplaces, letting you distribute custom-built or approved plugins exclusively within your organisation.

Organisation skills

Deploy custom skills across your organisation:

1. Create the skill (SKILL.md with YAML frontmatter)
2. Upload via admin settings
3. Set default enable/disable
4. Skills are available to all team members

Use this for: company terminology, standard processes, brand guidelines, report templates.

Connector management

Admins can:

• Pre-approve specific connectors for the organisation
• Add custom MCP server URLs for internal tools
• Restrict which connectors users can add on their own
• Set granular connector permissions per team or role

Enterprise Cowork controls

Enterprise plans include additional Cowork governance features:

• RBAC (role-based access control) for Cowork access and permissions
• Spend limits to cap usage at the team or user level
• Analytics dashboard for Cowork usage patterns
• OpenTelemetry integration for observability and monitoring
• Granular connector permissions scoped per team or role

Global instructions

Create an organisation-wide CLAUDE.md that applies to all Cowork sessions:

# [Company Name]: Claude Guidelines

## Company Context
- We're a [description] company
- [key facts Claude should always know]

## Standards
- Use Australian English
- All financial figures in AUD unless specified
- Client-facing content must follow our brand guide

## Compliance
- Never include customer PII in Claude outputs
- Financial projections require CFO review
- Legal documents require counsel review before execution

How to set it up

1. Configure seats

   1. Log into the admin dashboard
   2. Invite team members by email
   3. Assign Standard or Premium seats
   4. Set up any team/department groupings

2. Provision baseline plugins

   1. Install Productivity plugin org-wide (enabled by default)
   2. Install function-specific plugins (Finance, Legal, Sales, PE Modelling, HR, Design, Operations, etc.) as optional
   3. Communicate to team which plugins are available

3. Connect shared tools

   1. Set up organisation-level connectors (Slack, Asana, etc.)
   2. Configure which connectors are pre-approved
   3. Add custom MCP servers for internal tools if applicable

4. Deploy organisation skills

   1. Create a company CLAUDE.md with global instructions
   2. Upload any organisation-specific skills
   3. Test with a small group before org-wide deployment

5. Set usage guidelines

   1. Document model recommendations (Sonnet default, Opus for complex tasks)
   2. Share Cowork vs. Chat guidance
   3. Communicate security and compliance expectations
   4. Provide training resources (point to Your First 30 Minutes)

Related

• Team Rollout: the full deployment workflow
• Cost Management: optimise spend across seats
• SSO & Access Controls: enterprise authentication
• Security & Compliance: data handling and compliance
• Switching from ChatGPT: if your team is migrating from ChatGPT

---

Something wrong or outdated? Let us know →

Get weekly workflows: subscribe to the newsletter.