Skip to main content

Buildings Tab

The Buildings tab is where districts define and manage their physical locations inside Manage1to1. Buildings are foundational to how inventory, carts, incidents, checkouts, and reporting work together, so spending a little time configuring them correctly upfront pays off quickly.

Buildings typically represent schools, campuses, warehouses, or other district-managed locations where devices are stored, issued, repaired, or audited.

Permission Required

To access the Buildings tab, you need the Manage Settings permission assigned to your role.

Understanding Buildings​

Think of buildings as the organizational backbone of your Manage1to1 system - every user, device, and cart must be assigned to a building, and buildings enable location-based permissions, reporting, and workflows.

Why buildings are important:

  • Organization - Structure users and devices by physical location
  • Permissions - Control who can see/edit data for specific buildings
  • Reporting - Filter and group reports by school or facility
  • Integration - Match SIS data to correct locations during imports
  • Workflows - Track device movement between buildings

Key concept: Buildings are not just informational labels - they're functional units that control access, enable filtering, and organize data across the entire platform.

Building Management Overview​

The main Buildings screen provides a centralized list of all buildings configured in your district. From here, administrators can add new buildings and review and modify existing ones.

What you'll see:

  • List of all buildings
  • Building names
  • SIS/OneRoster IDs
  • Address information
  • Edit/delete actions

How to access:

  1. Navigate to Settings > System Settings
  2. Select Buildings tab
  3. View list of existing buildings
  4. Click Add to create new building or click building name to edit

Managing Buildings​

Buildings represent the physical schools or facilities within a district. They are used throughout Manage1to1 to organize users, devices, incidents, reporting, and invoicing.

The same configuration fields are used whether you are adding a new building or updating an existing one, which keeps management consistent over time.

Building Configuration Fields​

The following fields are available when creating or editing a building.

Building Name​

The Building Name is the primary label used across Manage1to1. It appears in user profiles, device assignments, incident records, and reports.

Best practices:

  • Use official school name (as recognized by families and staff)
  • Be consistent with SIS naming (reduces confusion)
  • Avoid abbreviations unless universally understood

Examples:

  • "Lincoln Elementary School"
  • "Washington High School"
  • "District Technology Center"
  • "Central Warehouse"

Important: Renaming a building does not break existing relationships. Devices, users, and incidents remain associated with the building after the name is updated.

SIS / OneRoster ID​

The Building SIS / OneRoster ID is used for automated imports and data matching when integrating with an SIS or OneRoster source, or when uploading via CSV files.

What it is:

  • Unique identifier from your Student Information System
  • Used to match import data to correct building
  • Essential for automated SIS sync

Examples:

  • "001" - Elementary school code in SIS
  • "HS01" - High school code
  • "9999" - District office or administrative facility

Important: This value should match the identifier used by your source system. If a building code changes in the SIS, it should be updated here to ensure imports continue to associate users and devices correctly.

Mismatch problems: If SIS ID doesn't match, automated imports may:

  • Create duplicate buildings
  • Fail to associate users to correct building
  • Require manual cleanup

Alternative Building IDs​

Alternative Building IDs allow a building to be matched using multiple identifiers.

When to use: Alternative IDs are helpful in situations where a single building location is represented by multiple SIS codes or identifiers.

Common scenarios:

  • Shared facilities: All users housed at the "Primary District Office," but data source feeds building codes 9001, 9002, 9003, and 9004 for separate departments within the same building
  • Legacy codes: Old SIS building codes that still appear in some data sources
  • Multiple systems: Different identifiers from finance systems, facilities management, etc.
  • SIS migrations: Temporary overlap during transition from old to new SIS

How alternative IDs work: During import, if a record contains building ID "9001" or "9002" or "9003," all match to the same building in Manage1to1.

Format: Enter alternative IDs as comma-separated list: 9001,9002,9003,9004

Alternative IDs are optional but improve matching reliability during automated updates.

Address Information​

Address fields store the physical location of the building. These fields are informational but may be referenced in reports and invoicing workflows.

Fields available:

  • Street address
  • City
  • State
  • ZIP code

When address matters:

  • Printing invoices with building-specific address
  • Generating reports requiring location data
  • Facilities management integration
  • Compliance documentation

Note: Address changes do not affect device or user assignments.

Use Building Address for Invoices​

When enabled, invoices associated with this building will use the address specified here instead of the district's primary address.

When to enable:

  • Building handles its own billing (decentralized districts)
  • Invoices should appear to come from specific school
  • Mailing address differs from district office

When to disable:

  • Billing is handled centrally (most common)
  • District office address should appear on all invoices

Example use case: Multi-campus district where each high school manages its own device billing. Each high school has this enabled so invoices show the school address, not the district office.

How Buildings Are Used Across the Platform​

Once configured, buildings become deeply integrated into daily workflows:

User management:

  • Users must be assigned to a specific building
  • Building determines which staff can view/edit user
  • Reports can be filtered by building

Device management:

  • Devices can be assigned to specific buildings
  • Track device location and movement
  • Building-level device inventory reports

Cart management:

  • Carts assigned to buildings
  • Building determines cart visibility
  • Track cart location

Incident tracking:

  • Incidents tracked by building location
  • Building-specific incident reports
  • Compare incident rates across buildings

Reporting:

  • Reports can be filtered or grouped by building
  • Building-level statistics and analytics
  • Cross-building comparisons

Automated imports:

  • Users automatically assigned to buildings based on SIS ID matching
  • Devices can be auto-assigned during bulk import
  • Building assignments update automatically during SIS sync

Because buildings touch so many areas, changes made here are reflected immediately across the system.

Permissions and Visibility​

Access can be limited on a per-building level. This is perfect for districts in which certain staff members need only delegated access to specific buildings.

How building-level permissions work:

  • Administrator roles can be restricted to specific buildings
  • Admins only see users, devices, and data for their assigned buildings
  • District-level admins see all buildings

Example:

  • Principal Smith: Access only to "Lincoln Elementary" building
  • IT Director Jones: Access to all buildings
  • Secretary Brown: Access to "Washington High School" building only

Important for setup: Please keep this in mind when setting up buildings - it is important that Users, Devices, and Carts also get tied to the appropriate buildings for building-level permissions to work correctly.

Building access configuration:

  • Set in Admin user configuration (see Administrators Documentation)
  • Assign buildings when creating or editing admin accounts
  • Remove building access to revoke visibility

Automated Import Considerations​

If your district uses automated SIS or OneRoster imports, building fields may be updated automatically based on source data.

What gets updated automatically:

  • Building name (if SIS provides updated name)
  • SIS ID (if configured to sync)
  • User assignments to buildings
  • Potentially address fields (depending on integration configuration)

If a building appears to revert after manual changes:

  1. Confirm the SIS / OneRoster ID matches the source system
  2. Review import mappings for building data
  3. Ensure the building is not being overwritten by scheduled imports

How to prevent overwrites:

  • Coordinate with IT staff managing SIS integration
  • Document which fields should remain manually managed
  • Consider whether manual changes should be made in SIS instead

Important: Automated imports always take precedence to maintain data consistency across systems.

Common Building Scenarios​

Adding a New School Building​

District opens a new elementary school:

  1. Navigate to Settings > System Settings > Buildings tab
  2. Click Add Building
  3. Configure fields:
    • Building Name: "Roosevelt Elementary School"
    • SIS ID: "006" (as provided by SIS team)
    • Address: Street, City, State, ZIP
    • Use Building Address for Invoices: Disabled (billing handled centrally)
  4. Click Save
  5. Building appears in list
  6. Assign users and devices to new building
  7. Configure building access for relevant administrators

Result: New building ready for users, devices, and operations.

Consolidating Multiple Buildings​

District closes two elementary schools and consolidates into one:

Before: "North Elementary" (SIS ID: 003) and "South Elementary" (SIS ID: 004) After: "Lincoln Elementary" (SIS ID: 005, new consolidated school)

Steps:

  1. Add new building "Lincoln Elementary" with SIS ID "005"
  2. Add alternative IDs: 003,004 (so old IDs still match)
  3. SIS sends users with building ID "003" or "004"
  4. Users automatically assigned to "Lincoln Elementary"
  5. Manually reassign any devices from old buildings to new building
  6. Optionally: Mark old buildings as inactive or delete (if no historical data needed)

Result: Consolidated school configured, old building codes still recognized during imports.

SIS Building Code Changes​

SIS changes building code from "HS-001" to "1001":

Problem: Automated imports start failing or creating duplicate building

Solution:

  1. Edit building in Manage1to1
  2. Update SIS/OneRoster ID from "HS-001" to "1001"
  3. Add Alternative Building ID: "HS-001" (preserves old code temporarily)
  4. Save
  5. Future imports use new code, old imports (if any) still match

Result: Smooth transition without data disruption.

Common Questions​

Q: Can I delete a building? You can delete buildings that have no associated users, devices, or historical data. Buildings with associations typically cannot be deleted to preserve data integrity. Consider marking as inactive instead.

Q: What happens to users and devices if I delete a building? Most systems prevent deletion if associations exist. If deletion is allowed, users/devices may become unassigned or orphaned, causing data integrity issues.

Q: Can I rename a building without breaking anything? Yes. Renaming a building updates the display name throughout the system but doesn't break relationships. Users, devices, and incidents remain associated with the building.

Q: Why do I see buildings I don't recognize?

  • SIS may be sending building codes for programs, departments, or facilities not traditionally thought of as buildings
  • Old buildings from previous years may still exist
  • Test buildings from initial setup

Check with SIS administrator to understand unexpected building codes.

Q: What if a building doesn't have an SIS ID?

  • Buildings without SIS ID cannot be auto-matched during imports
  • Users/devices must be manually assigned
  • Not critical for buildings that don't receive SIS data (warehouses, district offices)

Q: Can buildings share the same SIS ID? No. Each building should have a unique SIS ID. Use Alternative Building IDs if multiple codes should map to the same building.

Q: Do I need to create a building for the district office? If you have staff users or devices assigned to the district office, yes. Otherwise, optional.

Q: Can I change a building's SIS ID mid-year? Yes, but coordinate with SIS integration staff. Ensure new ID matches what SIS is sending, and add old ID as alternative ID for transition period.

Q: What's the difference between SIS ID and Alternative IDs?

  • SIS ID: Primary matching identifier from your SIS
  • Alternative IDs: Additional identifiers that also match to this building (comma-separated list)

Both are used during imports to match data to the correct building.

The Buildings tab provides foundational structure for your Manage1to1 implementation. Properly configured buildings enable accurate data organization, effective permissions management, reliable SIS integration, and meaningful reporting across your district.

Last updated on