Snipe-IT Version
v8.1.16 - build 18612
How can we help?
Snipe-IT’s current Full Multiple Company Support is built on MSP (Managed Service Provider) logic, where "Company A" and "Company B" are treated as strictly segregated tenants. While this is ideal for external client separation, it creates a significant roadblock for single enterprises managing internal complexity (e.g., Departmental Orgs, Government Contracts, or Partner-Furnished Equipment).
In high-compliance environments, the current architecture forces a choice between two suboptimal workarounds:
- Instance Sprawl: Deploying multiple separate Snipe-IT instances to satisfy individual contract/org audit requirements. This results in fragmented data, massive administrative overhead for LDAP/SAML syncing, and a loss of a global "Single Pane of Glass."
- Security & Compliance Compromise: Granting Project Managers or Contract Leads "Global Admin" access so they can manage their specific assets. This violates the Principle of Least Privilege, as they gain visibility into assets and organizations far outside their scope.
Ultimately, the system currently prevents a single user from easily holding assets from different "Companies" without breaking the "Full Company Support" security model.
Proposed Solution: The Three Pillars of Unified Management
1. Structural Flexibility: Rebranding "Companies" to "Organizations"
To better reflect enterprise use cases, the terminology should shift from external clients to internal entities.
The Change: Introduce a global UI toggle to rebrand "Companies" to "Organizations," "Contracts," or "Entities."
The Purpose: This aligns the system with internal audit realities, where an employee belongs to the Parent Company but utilizes gear owned by specific Contract Organizations.
2. Functional Fluidity: Cross-Org Checkout & Unified User View
The hard-wall between companies needs to become "permeable" for the end-user.
The Change: Enable a mode where a user’s "Home Organization" does not prevent them from being assigned assets from a different Organization.
The Result: A "Single Pane of Glass" for the employee. When a user logs in, they see one consolidated list of all equipment—e.g., their internal IT laptop and their specialized contract-funded hardware—in a single view.
3. Scoped Governance: The "Org-Admin" Role
To eliminate administrative bloat and improve security, we need delegated authority.
The Change: Create a per-organization administrative role. This allows a user (like a PM or Contract Lead) to be granted Admin permissions restricted strictly to their assigned Organization.
The Purpose: A PM for "Contract A" can manage, audit, and report on their specific inventory without needing "Super Admin" access or seeing data from "Contract B" or "Internal IT."
Strategic Value
Eliminates Infrastructure Sprawl: Consolidates management into one instance, reducing the need to patch, backup, and maintain multiple deployments.
Audit-Ready Architecture: Maintains the granular "Siloed Reporting" required by compliance officers while providing "Global Visibility" for the enterprise.
Operational Efficiency: Empowers non-IT managers (PMs/Contract Leads) to manage their own gear within a controlled, scoped environment.
Improved UX: End-users have a single source of truth for all equipment they are accountable for, regardless of the funding source or internal owner.
Code of Conduct
Snipe-IT Version
v8.1.16 - build 18612
How can we help?
Snipe-IT’s current Full Multiple Company Support is built on MSP (Managed Service Provider) logic, where "Company A" and "Company B" are treated as strictly segregated tenants. While this is ideal for external client separation, it creates a significant roadblock for single enterprises managing internal complexity (e.g., Departmental Orgs, Government Contracts, or Partner-Furnished Equipment).
In high-compliance environments, the current architecture forces a choice between two suboptimal workarounds:
Ultimately, the system currently prevents a single user from easily holding assets from different "Companies" without breaking the "Full Company Support" security model.
Proposed Solution: The Three Pillars of Unified Management
1. Structural Flexibility: Rebranding "Companies" to "Organizations"
To better reflect enterprise use cases, the terminology should shift from external clients to internal entities.
The Change: Introduce a global UI toggle to rebrand "Companies" to "Organizations," "Contracts," or "Entities."
The Purpose: This aligns the system with internal audit realities, where an employee belongs to the Parent Company but utilizes gear owned by specific Contract Organizations.
2. Functional Fluidity: Cross-Org Checkout & Unified User View
The hard-wall between companies needs to become "permeable" for the end-user.
The Change: Enable a mode where a user’s "Home Organization" does not prevent them from being assigned assets from a different Organization.
The Result: A "Single Pane of Glass" for the employee. When a user logs in, they see one consolidated list of all equipment—e.g., their internal IT laptop and their specialized contract-funded hardware—in a single view.
3. Scoped Governance: The "Org-Admin" Role
To eliminate administrative bloat and improve security, we need delegated authority.
The Change: Create a per-organization administrative role. This allows a user (like a PM or Contract Lead) to be granted Admin permissions restricted strictly to their assigned Organization.
The Purpose: A PM for "Contract A" can manage, audit, and report on their specific inventory without needing "Super Admin" access or seeing data from "Contract B" or "Internal IT."
Strategic Value
Eliminates Infrastructure Sprawl: Consolidates management into one instance, reducing the need to patch, backup, and maintain multiple deployments.
Audit-Ready Architecture: Maintains the granular "Siloed Reporting" required by compliance officers while providing "Global Visibility" for the enterprise.
Operational Efficiency: Empowers non-IT managers (PMs/Contract Leads) to manage their own gear within a controlled, scoped environment.
Improved UX: End-users have a single source of truth for all equipment they are accountable for, regardless of the funding source or internal owner.
Code of Conduct