# Managing Claude Code at work — retained record

> Retained reddit record from reddit:ClaudeCode.

Canonical: https://highsignal.app/data/records/5b600c1952ab2851

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeCode)  published 2026-11-18 17:51 ingested 2026-11-19 02:39

[original source ↗](https://www.reddit.com/r/ClaudeCode/comments/1xzlrva/managing_claude_code_at_work/)

## retained text



```
Hi everyone,

I work at a small non-tech creative firm and have been leading AI implementation for the last 3 years, which has largely been chatbots, knowledge work, etc.  I do a lot of AI assisted coding outside the office, and am fairly familiar with it, but so far have been the only one doing it at work.

For the longest time, most of our team including leadership has been relatively uninterested in AI for coding. So I've been unable to get as far as I would've liked, until now.

That has changed in recent months; in part due to my efforts to present the options, in part because we got a new IT manager, and in part because recent capabilities have made vibe coding very accessible for people with no software experience, and it has been in the news.

People at the firm are really excited about it now, and I'm seeing a new level of interest. It's great, and I'm really happy to see it, but it also raises some concerns. We have people vibe coding stuff a lot now, and leadership is getting excited about one shot demos, which are great, but in their current form unmaintainable and questionably secure.

I've been tasked with managing this across the company and basically given the go ahead to work with our new IT consultant to do "all the technical stuff to make the thing happen." They want to see these tools being used more broadly around the office, and I want to support that in a controlled way.

I am thinking about a company GitHub organization, access controlled logins for Code (everyone has Cowork, only some get Code), and policy around where development occurs, how repos are maintained, standard repo settings and CI - basically a simple set of checks and balances to make it a lot harder for people to accidentally, say, host company data on a public site, or mess up a project by accident. Beyond that, we're talking about establishing some rules about what kind of data is allowed to be used for these purposes, and how far we should allow people to take these projects (simple web tools to help with work, great, complex software people rely on for serious stuff, too far out over our skis.)

We don't really have software "in production" per se, but as the org's GitHub admin I would review PRs and make sure everything is tidy before it gets hosted officially for internal use.

Have others here set this kind of thing up at their companies outside the software industry? What would your advice be for someone in my position?
```



document fetched 2026-11-19 00:41 · canonical https://reddit.com/r/ClaudeCode/comments/1xzlrva/managing_claude_code_at_work
