Skip to content

Collaboration — MapBoot Documentation

Collaboration is designed for teams building large, complex venues (e.g., convention centers, campuses, hospitals) where multiple buildings and many floors make single‑user mapping slow and error‑prone. Collaboration lets an owner split work across teammates while keeping data safe and organized.

How Collaboration Works (Overview)

  • The Owner creates the map and overall structure (buildings/groups and floors).
  • The owner adds collaborators in the Dashboard by email.
  • Only registered users with confirmed accounts can be approved.
  • The owner assigns specific floors to each collaborator.
  • Collaborators see the map under “Collaboration Maps” in their account.
  • Collaborators can edit only the floors assigned to them.
  • Cross‑floor or cross‑building transition links that affect unassigned floors must be created by the owner (or by a collaborator only between their own assigned floors).

Typical Workflow

  1. Owner creates a map
  2. Start a new map and name it.

  3. Add groups (buildings) and create the floors (layers) for each building.

  4. Add collaborators (Dashboard)

  5. Go to Dashboard → Collaborations.
  6. Enter user emails to invite as collaborators.

  7. Users must be registered and confirmed; otherwise they won’t be approved.

  8. Assign floors to collaborators

  9. Open the map in the Editor.
  10. In the tree, click the floor you want to assign.

  11. In the floor’s Properties, select the collaborator’s email from the list and Save.

  12. Collaborator edits

  13. The assigned map appears under Collaboration Maps for the collaborator.
  14. They can edit only their assigned floors.

  15. If they have multiple floors assigned, they may create transitions between those assigned floors.

  16. Owner connects across floors/buildings (if needed)

  17. Transitions that involve unassigned floors or other buildings must be performed by the owner.
  18. Example: Outside (transition) paths linking Building A to Building B.

Permissions & Limits

Action Owner Collaborator
Create/Delete Map ✅ ❌
Add/Remove Buildings (Groups) ✅ ❌
Add/Remove Floors (Layers) ✅ ❌
Edit Assigned Floors ✅ ✅ (assigned only)
Edit Unassigned Floors ✅ ❌
Create Transitions Between Assigned Floors ✅ ✅ (assigned only)
Create Transitions Involving Unassigned Floors/Buildings ✅ ❌
Publish / Finalize ✅ ❌

Notes
- Collaborators cannot change subscription‑limited items (e.g., number of buildings/floors beyond plan limits).
- The owner retains full control over structure and publication.

Best Practices

  • Front‑load structure: The owner should create buildings and floors before assigning work.
  • Assign by floor: Use clear naming (e.g., Building A — First Floor) to make ownership obvious.
  • Keep transitions clean: Collaborators can link their own floors; the owner handles cross‑building or unassigned floors.
  • Review regularly: Owners should review collaborator changes and test A→B routing across floors and buildings.
  • Save often: Remind collaborators that unsaved work can be lost on refresh/navigation.

Troubleshooting

  • Collaborator can’t see the map
    Ensure their account is registered and confirmed, and that at least one floor is assigned.

  • Collaborator can’t edit a floor
    Verify the floor is assigned to that user .

  • Transitions don’t work across buildings
    Owner should verify Outside (transition) group paths exist and that transitions are created Building ↔ Outside ↔ Building.

For help with collaboration setup or to request bulk assignment tools, email contact@mapboot.com.