How to decide who gets access to workplace AI tools
Organizations are struggling to figure out how to license AI tools fairly while controlling costs across different departments. Without a clear rollout strategy, companies face security risks from employees plugging sensitive information into public models and unmonitored shadow IT connections spreading across development teams.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
How to decide who gets access to workplace AI tools
- 1Having department heads decide access and pay from their own budgets instead of IT'sDid this help you?
- 2Requiring users to demonstrate a specific use case or proof of needDid this help you?
- 3Routing Azure subscription charges directly through department credit cardsDid this help you?
- 4Writing up employees who violate policyDid this help you?
- 5Using HasMCP to build MCP servers from OpenAPI specs with different privilegesDid this help you?
- 6Enforcing basic DevOps and SRE discipline to prevent direct changesDid this help you?
- 7Using copilot licenses bundled with Microsoft subscriptionsDid this help you?
- 8Deploying self-hosted open-webui instances with litellm and ZDR policiesDid this help you?
- 9Setting up isolated instances in Azure with no internet accessDid this help you?
- 10Using monitoring tools like Harmony to detect and block unauthorized AI usageDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“As a 1-month fresh IT engineer I inherited a lot of stuff at a company, and we're just now looking into how we should provide premium ChatGPT licences for our workers.”source ↗
“I’m interested in hearing from you guys about how you’re handling AI adoption across your organization.”source ↗
“If you’re not licensing everyone, how are you deciding who gets access?”source ↗
“How are you preventing employees from entering sensitive, confidential, customer, financial, or proprietary information into AI tools?”source ↗
“Devs here started connecting Claude and Cursor to MCP servers on their own and now I have to put some control around it before it spreads further.”source ↗
Where this came up
People with this problem also raised
- 9How to audit employee AI tools and browser extensions
- 7How to secure and support internal AI apps built by non-technical employees
- 4How to use AI in grant writing without getting flagged
- 26Why am I being forced to use AI at work?
- 2Why won't Claude connect to Salesforce?
- 7How do you enable record updates in Agentforce and check credit costs?