Enterprise access
Claude access and subscriptions are provided through the enterprise.
Users should not create independent paid subscriptions or bypass enterprise access controls for business work.
Requesting additional token capacity
If the available capacity does not support the required workload:
- Open AI Lens in 1C
- Create a new workstream and raise request by describing the business problem and other details
- Describe the business problem and expected outcome
- After the workstream is approved you can raise request for more tokens under that workstream
- Provide the reason for requesting more tokens
- Submit the workstream for enterprise review and approval
Information to include
Business value
Explain the problem, expected outcome, target users, measurable benefit, and delivery timeline.
For: Why the capacity is required
Usage forecast
Estimate users, requests, input size, output size, usage frequency, and expected growth.
For: Expected token demand
Developer Impact
Declare targets from two perspectives - for the team building this, and for the people it will serve.
For: Expected run time impact
Status Context
Where is it in the lifecycle and anything worth capturing ?
For: Work in progress or completed
Responsible-use requirements
Before using Claude for enterprise work:
- Confirm that the approved Claude environment is being used
- Follow project, customer, privacy, security, and data-handling policies
- Do not paste credentials, tokens, private keys, or passwords
- Do not submit restricted data without explicit approval
- Apply least-privilege access to MCP servers and external tools
- Review generated code and business recommendations
- Validate important facts and calculations
- Test all generated code before deployment
- Maintain human approval for consequential actions
- Report suspected data exposure or unsafe behavior through approved channels
Final learning checklist
You have completed installation, Claude for Work, Claude Code, Git workflows, MCP, instructions, Skills, hooks, subagents, advanced workflows, and enterprise-access guidance.
Do not submit confidential information, credentials, restricted customer data, or proprietary source code unless the approved enterprise environment and applicable policies explicitly permit the information.