Server And Code Access Policy
1. Purpose
This policy defines who is permitted to access, modify, or work with iTech-developed systems, customizations, and proprietary enhancements.
This policy is separate from the iTech Support Policy and applies specifically to agency partnerships and code-level access.
2. Code Governance & Intellectual Property
While the core CRM framework may be open-source, all iTech customizations, structural modifications, integrations, proprietary enhancements, plugins, architectural configurations, and performance optimizations are protected under iTech intellectual property and internal business standards.
Access to such components is restricted and governed by this policy.
3. Who May Access iTech Code
Access is strictly limited to:
iTech-Approved Agencies
Only agencies formally reviewed and approved by iTech may request structured development access.
Approval is discretionary and not automatic.
4. Agency Qualification Requirements
To be considered for approval, an agency must submit:
- Full organizational team structure
- First and last name of each technical team member
- Role and title of each member
- Professional profile (LinkedIn or equivalent)
- Relevant certifications (if applicable)
- Registered business documentation
- Signed confidentiality and intellectual property agreements
Incomplete submissions will not be reviewed.
iTech reserves full authority to approve or decline any application.
5. Development Standards Compliance
All approved agencies must comply with iTech technical and architectural standards, including but not limited to:
- Code structure and file organization
- Version control requirements
- Security protocols
- API standards
- Naming conventions
- Documentation procedures
- Deployment workflow
- Change tracking and logging
Non-compliant code may be:
- Rejected
- Rolled back
- Removed
- Billed for correction
- Cause for access suspension
6. Coordination & Supervision
All approved agencies must:
- Coordinate development activities in writing
- Document all changes
- Submit structured deployment plans
- Follow approval workflows when required
Unsupervised modifications are not permitted.
7. Restrictions
The following actions are strictly prohibited:
- Unauthorized access to infrastructure
- Reverse engineering proprietary enhancements
- Code duplication or redistribution
- Resale or rebranding of iTech proprietary components
- Deployment outside licensed environments
- Sharing access credentials with unauthorized personnel
8. Termination of Agency Authorization
iTech reserves the right to immediately suspend or terminate agency authorization under the following circumstances:
- Violation of coding standards
- Unauthorized access or system modification
- Breach of confidentiality or intellectual property agreements
- Misrepresentation of agency credentials
- Failure to comply with governance procedures
- Interference with system stability or security
- Non-payment of agency licensing fees (if applicable)
Termination may occur without prior notice if the violation poses risk to system integrity, data security, or intellectual property.
Upon termination:
- All access credentials will be revoked immediately
- All development privileges will cease
- Agency licensing rights will be suspended or canceled
- Ongoing projects may be halted pending review
9. Legal Enforcement & Liability
Unauthorized access, misuse of proprietary components, code duplication, redistribution, reverse engineering, or structural replication of iTech customizations constitutes a breach of intellectual property protection.
iTech reserves the right to pursue:
- Civil legal action
- Financial damages
- Injunctive relief
- Contract enforcement remedies
- Recovery of legal costs and associated expenses
Agencies found in violation may also be held financially responsible for:
- System remediation costs
- Security audit expenses
- Code reconstruction
- Operational losses resulting from unauthorized actions
10. Governance Authority
iTech retains sole authority over:
- Code access approval
- Architectural direction
- Version governance
- Infrastructure standards
- Technical compliance validation
Approval as an agency does not transfer ownership of proprietary components.
11. Acceptance
By applying for or operating as an iTech-approved agency, the organization agrees to comply fully with this Agency Authorization & Code Access Policy.
Good. This is important — because governance without infrastructure control is weak.
Below is a clean section you can add to your Agency Authorization & Code Access Policy under a new heading.
It is structured, technical, and enforceable.
12. Server & Infrastructure Access Requirements
To maintain system integrity, data security, and version control consistency, the following server requirements apply to all iTech-approved agencies.
12.1 Exclusive Developer Access
The production server environment must be accessible only to:
- Approved agency developers
- Authorized iTech technical personnel (if applicable)
Access must not be shared with:
- Non-technical employees
- Administrative staff
- Marketing teams
- External vendors
- Unapproved third parties
Credential sharing outside authorized developers is strictly prohibited.
12.2 Shared Infrastructure Safeguards
If the server environment is shared with other business functions or third-party providers, the following technical isolation measures are mandatory:
A. CLI & SSH-Only Developer Access
Approved developers must access the server exclusively through:
- Secure CLI access
- SSH with key-based authentication
- No shared hosting control panels for production modification
Root access must be controlled and logged.
B. Remote or Restricted Database Access
The database must not be publicly accessible.
The following is required:
- Remote database access restricted by IP allowlist
- No public database ports exposed
- Database credentials not stored in plain text
- Access limited to application layer or secured SSH tunnel
Database visibility must be restricted to authorized developers only.
C. Isolated File & Folder Containerization
File systems must be logically isolated to prevent unauthorized visibility.
This may include:
- Containerized deployment environments
- Restricted file permission structures
- Segmented directory access
- Role-based file access control
- No public browsing of application directories
Non-developer staff must not have visibility into application core files, proprietary enhancements, or system configuration directories.
12.3 Logging & Monitoring
All developer access must be:
- Logged
- Traceable
- Auditable
Unauthorized login attempts or access escalation must trigger review.
12.4 Non-Compliance
Failure to maintain these infrastructure requirements may result in:
- Suspension of agency authorization
- Temporary suspension of SLA coverage
- Required security revalidation before support resumes
- Liability adjustment for security breaches
iTech reserves the right to request infrastructure validation prior to granting or maintaining agency access.
