Service · Claude setup

We set up Claude for your organization.

Claude Team or Enterprise, with Claude Code for your developers. One company account, shared skills and rules, and coding agents that follow them. You approve the plan, and you keep everything.

  • 01You approve every changeNothing is switched on before you have read the plan.
  • 02No passwords or API keysWe work alongside your admin. Keys and billing stay with you.
  • 03You keep everythingFiles, settings and the runbook are yours, in your repository.

The problem

Sound familiar?

01Adoption

Everyone uses Claude differently

The seats are paid for, but each person writes their own prompts and nothing is shared.

02Coding agents

Coding agents with no rules

Developers run Claude Code on company code, and nothing stops it reading a .env file or pushing to main.

03Security

Security has questions

Who can sign in, where data goes, what agents may do. Nobody has written answers.

04Time

No time for the admin console

SSO, roles, skills, connectors, agent policies: days of documentation that changes every few months.

We fix all four in your own Claude organization, and hand it over ready to use.

The result

What your company gets.

01

One company account

Everyone signs in with their work email. Switch someone off in your directory and they can no longer sign in.

02

Shared skills and rules

Your templates, brand voice and procedures built in once. Every chat starts from your company’s instructions.

03

Coding agents that follow your rules

No access to secrets, a question before every push, only approved tools. Enforced on every laptop.

04

Your tools, connected safely

Drive, Slack, GitHub or your CRM, with reading allowed and anything that writes waiting for approval.

05

Usage and cost you can see

Spend limits and usage analytics, so you know who uses what and what it costs.

06

Everything written down

Every setting, skill and rule in your own repository, with a runbook. No lock-in.

The settings

What we set up in Claude.

The settings in Claude’s admin console and in Claude Code that we configure for you. Some need Enterprise, and we tell you before you buy.

Checked against Anthropic’s documentation and pricing on 30 October 2026.

01 / Access

Who gets in, and how.

  • Single sign-on
  • Domain verification
  • Standard & Premium seats
  • Domain captureEnterprise
  • SCIM provisioningEnterprise
  • Custom rolesEnterprise
  • IP allowlistingEnterprise

02 / Shared knowledge

Instructions every chat starts from, up to 3,000 characters, and skills everyone gets.

  • Organization instructions
  • Organization skills
  • Plugins for groups
  • Shared projects

03 / Connectors & features

Each connector tool set to Always allow, Needs approval or Blocked.

  • Per-tool connector permissions
  • Web search
  • Code execution
  • Cowork

04 / Claude Code

Rules a developer or a cloned repository can’t loosen.

  • Managed settings
  • Permission rules
  • Hooks
  • Approved MCP servers
  • Company-only login
  • managed-settings.json via MDM
  • managed-mcp.json
  • OpenTelemetry metrics
managed-settings.jsonExample
{
  "permissions": {
    "deny": ["Read(./.env)", "Read(./secrets/**)"],
    "ask": ["Bash(git push *)"],
    "disableBypassPermissionsMode": "disable"
  },
  "forceLoginOrgUUID": "your-organization-id"
}

05 / Spend

Know who uses Claude, and what it costs.

  • Per-user spend limits
  • Organization spend limit
  • Usage analytics

06 / Compliance

For security and legal teams.

  • Audit logsEnterprise
  • Compliance APIEnterprise
  • Custom data retentionEnterprise
  • Analytics APIEnterprise

Set up by

Claude Certified Architects.

Our specialists hold Anthropic’s Claude Certified Architect certification, a proctored exam on designing systems with Claude Code, the Claude API, the Agent SDK and MCP. We also run this setup ourselves: this site is built every day with Claude Code, shared skills and written rules.

The process

How it works.

  1. Step 01

    You write to us

    Tell us what you use and what you need.

  2. Step 02

    We draft a plan

    Every setting, skill and rule we propose, in writing.

  3. Step 03

    We agree it

    Nothing starts until you approve the plan.

  4. Step 04

    We do the work

    In your own Claude organization, alongside your admin.

  5. Step 05

    We hand it over

    A ready setup, with every file and setting written down.

FAQ

Questions.

Something else? Write to team@laxima.tech.

How do I set up Claude for my organization?

Choose Claude Team or Enterprise, verify your domain, connect single sign-on and invite people. Then write organization instructions, provision shared skills, set connector permissions and, if developers use Claude Code, push managed settings that every machine follows. You can do it yourself from Anthropic’s documentation, or we do it for you and hand everything over.

Do we need Claude Team or Enterprise?

Team covers 2 to 150 seats with single sign-on, organization skills and instructions, and spend controls. Enterprise adds SCIM, domain capture, custom roles, audit logs, a compliance API and custom data retention. We recommend the smallest plan that covers what you actually need.

Can Claude Code be locked down on every developer’s machine?

Yes, with managed settings. On Team and Enterprise they are set once in the Claude admin console and every Claude Code session picks them up. With device management they can be deployed as a file. A developer or a cloned repository cannot loosen them.

Can you set up Claude for just one person?

Yes. On Claude Pro or Max we set up your preferences, personal skills and the rules Claude Code follows in every project.

Who does the setup?

Our specialists, who hold Anthropic’s Claude Certified Architect certification. We also run the same setup for our own work every day.

Do you need our passwords or API keys?

No. We work in your admin console alongside your admin, or through a temporary admin role you remove afterwards. Passwords, keys and billing stay with you.

Next step

Get Claude set up properly.

Tell us which Claude plan you have or plan to buy, roughly how many people, and whether developers use Claude Code. You get a plan and what it takes, usually within two business days.

Claude, Claude Code and Anthropic are trademarks of Anthropic.

Let's
Talk

Send it here and it lands in the editorial inbox. A few lines of context beat a long introduction. Tell us what you're looking at and what you need from us.