Multi-Tenancy (ish)
This guide explains how Snipe-IT restricts what users can see and do based on company membership. These features are designed for organizations that manage assets across multiple companies or business units and need to keep those companies' data separated.
Full Multiple Company Support
Setting: Admin → General Settings → Full Multiple Company Support
By default, all users with the appropriate permissions can see all assets, users, locations, and other records in Snipe-IT, regardless of which company they belong to.
When Full Multiple Company Support (FMCS) is turned on, Snipe-IT restricts what each user can see and manage based on company membership:
- A user assigned to Company A will only see assets, users, locations, and other records that also belong to Company A.
- A user assigned to Company B will only see records belonging to Company B.
- Records with no company assigned are handled separately (see Floater Mode below).
This restriction applies everywhere in the application - lists, searches, dropdowns, exports, imports, and the API.
Superusers are exempt
Users with the Superuser role always see everything, regardless of FMCS settings. This ensures that system administrators can manage the full installation without being locked out of any company's data.
Users can belong to multiple companies
A single user account can be a member of more than one company. When that user is logged in, they will see records from all of their companies combined.
Floater Mode
Setting: Admin → General Settings → Treat items and users without company associations as floaters
When FMCS is on, what happens to assets, users, and locations that have no company assigned? Floater mode controls this.
Floater mode OFF (default)
Records with no company are treated as belonging to their own invisible "null" company. They are only visible to other records that also have no company assigned.
- A user in Company A cannot see or interact with assets, users, or locations that have no company.
- An uncompanied user cannot see users or assets that belong to any company.
- An asset with no company can only be checked out to a user who also has no company.
This is the strictest mode and keeps uncompanied records fully isolated.
Floater mode ON
Records with no company are "floaters" — they float freely across company boundaries and are visible and usable by everyone.
- A user in Company A can see assets, users, and locations that have no company assigned, in addition to their own company's records.
- An uncompanied user can see everything.
- An asset with no company can be checked out to any user, regardless of company.
Use this mode when you have shared resources (spare laptops, a shared office location, a pool of accessories) that any company's users should be able to access.
Location Scoping
Setting: Admin → General Settings → Scope Locations with Full Multiple Company Support
This setting requires Full Multiple Company Support to be enabled first.
By default, even with FMCS on, any location can be assigned to any user or asset regardless of company. Location scoping tightens this rule.
When Location Scoping is turned on, a location can only be assigned to a user or asset if they belong to the same company as that location.
For example:
- "Marketing Storage Room" is assigned to Company A.
- A user in Company B cannot be placed in "Marketing Storage Room."
- An asset belonging to Company B cannot use "Marketing Storage Room" as its location.
If you try to save a user or asset with a mismatched location, Snipe-IT will show a validation error and prevent the save.
Locations with no company
Locations that have no company assigned follow the same floater rules:
| Floater mode | Can a user with a company be assigned a no-company location? |
|---|---|
| OFF | No |
| ON | Yes |
Compatibility check
Before you can turn on Location Scoping, Snipe-IT requires you to run a compatibility check. This scans your existing data for any users or assets that are already assigned to a location belonging to a different company. If conflicts are found, you will need to resolve them before the setting can be enabled — otherwise those existing records would immediately fail the new rule.
Quick reference
| FMCS | Floater | Location Scoping | What a Company A user can see | Can use a no-company location? |
|---|---|---|---|---|
| Off | — | — | Everything | Yes |
| On | Off | Off | Company A records only | No — no-company locations belong to their own invisible bucket |
| On | Off | On | Company A records only | No |
| On | On | Off | Company A + no-company records | Yes (location scoping is off) |
| On | On | On | Company A + no-company records | Yes |
Superusers always see everything regardless of the settings above.
