Resource Types

Detailed information about each type of resource you can add.

The admin portal resource builder with available resource type buttons highlighted:

Sections

Collapsible groups with headers that organize items on the same screen.

Best used for:

• Grouping related protocols together
• Creating categories (e.g., "Medical Protocols", "Fire Operations")
• Building a hierarchical navigation structure

Optional

Sections are not required. You can add pages, documents, and other resources directly without grouping them into sections if you prefer a simpler structure.

Example structure:

EMS DOCUMENTATION (Section)
├── Treatment Protocols (Page)
└── EMS Procedures (Page)
POLICIES (Section)
├── Personnel (Page)
└── Station (Page)
Additional Resources (Section)
├── Phone Directory (Page)
└── Web Links (Page)

The image shows how this menu structure appears in the mobile app, directly reflecting the configuration from the admin portal.

Configuring Sections:

• Title - The section title displayed in the app
• Default Expanded - Controls whether the section appears open or closed when first viewed

All sections can be expanded and collapsed by tapping them. The Default Expanded option only controls the initial state.

In the example below, the first three sections (ADMINISTRATION, EMS OPERATIONS, A SHIFT) start collapsed, while the last two (B SHIFT, C SHIFT) start expanded.

Pages

Navigable folders that act as containers for additional resources. When tapped, pages open a new screen displaying their contents.

Best used for:

• Organizing resources into logical groups (e.g., "Treatment Protocols", "Emergency Contacts")
• Creating multi-level navigation structures
• Separating content by department, shift, or category
• Building a browsable hierarchy of information

How Pages work:

Unlike Sections which expand/collapse in place, Pages navigate users to a new screen. This allows for deeper organization and keeps the main menu clean.

Example:

Additional Resources (Section)
├── Phone Directory (Page)
│   ├── Administration (Section)
│   │   ├── Chief - (555) 123-4567
│   │   └── Deputy Chief - (555) 123-4568
│   └── EMS Operations (Section)
│       ├── Medical Director - (555) 123-4569
│       └── EMS 1 Office - (555) 123-4570
└── Forms (Page)
    ├── Incident Report.pdf
    └── Equipment Check.pdf

In this example:

• Phone Directory is a Page - tapping it navigates to a new screen
• Inside Phone Directory are Sections (Administration, EMS Operations) with phone contacts
• Web Links is another Page containing url links

Options:

• Title - The page name displayed in the app

Key differences from Sections:

• Pages navigate to a new screen (like opening a folder)
• Sections expand/collapse in place (like an accordion)
• Pages show a folder icon and can be bookmarked
• Sections show a text header and cannot be bookmarked

Navigation:

When users tap a Page, they navigate into it and see a back button to return to the previous level. This allows for unlimited nesting depth.

Documents (PDFs)

Upload PDF files for your team to reference.

Best used for:

• Policies and procedures
• Protocol documents
• Reference guides
• Forms and checklists

Options:

• Title - Display name for the document
• File - The uploaded PDF file
• Start Page (optional) - Specify which page the PDF opens to by default

Understanding Start Page Option

The Start Page feature allows you to create multiple resources that reference different sections of a single master PDF document, rather than splitting large documents into separate files.

How it works:

When you set a Start Page number for a PDF resource, the mobile app automatically opens the PDF to that page. Users can still navigate to other pages within the document, but the resource will always open to your specified starting point.

Example use case:

You have a comprehensive "Master Protocols Manual" (100 pages) containing multiple protocols:

• Cardiac Arrest (Pages 1-20)
• Stroke Assessment (Pages 21-35)
• Trauma Management (Pages 36-55)
• Pediatric Emergency (Pages 56-75)
• Medication Reference (Pages 76-100)

Instead of creating 5 separate PDF files, you can:

1. Upload the master PDF once
2. Create 5 separate menu items
3. Set each resource to open at its section's starting page

Benefits:

• Simplified management - Maintain one document instead of many
• Reduced storage - Only one file to store and distribute

Important considerations:

Page Dependencies

Using Start Page creates a dependency between your menu structure and page numbers. If you reorder resources or add new ones between existing items, you may need to update multiple Start Page values.

Example scenario: If you have Protocols 1-5 set up and later add "Protocol 1A" between Protocol 1 and Protocol 2, the page numbers for subsequent protocols won't automatically update. You'll need to manually adjust them if the document structure changes.

Best practices:

• Plan your protocol organization carefully before setting up Start Pages
• Use descriptive names rather than numbers (e.g., "Stroke Assessment" instead of "Protocol 2")
• Document which resources share a master PDF and their page ranges
• Audit Start Page values when reorganizing your menu structure

When to use Start Page:

• Your protocol structure is stable and highly unlikely to change frequently
• You have a well-organized master document with clear sections
• The benefits of single-file management outweigh maintenance complexity

When to use separate PDFs wihtout page start instead:

• Protocols are frequently reorganized or reordered
• New protocols are regularly added between existing ones
• Different protocols have independent update schedules

---

Need help deciding? The Start Page feature can be confusing to set up properly, and choosing the wrong approach for your organization's needs can create maintenance challenges down the road. We recommend contacting our support team before implementing Start Pages for the first time. We'll help you evaluate your document structure and determine the best approach for your specific use case.

Web Links

Links to external or internal web pages.

Best used for:

• Online forms
• External reference sites
• Training videos
• Third-party tools

Options:

• Title - Display name for the link
• URL - The web address

Phone Contacts

Tap-to-call or text phone numbers.

Best used for:

• Dispatch numbers
• Poison control
• Hospital contacts
• EMS Staff
• Co-workers

Options:

• Title - Contact name or description
• Phone Number - The number to dial or text

Email Contacts

Tap-to-email addresses.

Best used for:

• Department contacts
• Report submission
• Support requests

Options:

• Title - Contact name or description
• Email Address - The email address