Appearance
Feature Reference
In-depth guide to features, settings, and permission requirements across all OneSiteKit portals. For getting-started guides see the individual feature pages.
Permission Levels
Every screen and action in OneSiteKit is gated by a combination of the user's account role and, where applicable, their portal-specific access level. The four account roles are fixed org-wide; portal-specific roles are assigned per-resource.
| Role | Applies To | Capabilities Summary |
|---|---|---|
| Admin | Org-wide | Full create/edit/delete across all portals. Manages users, org settings, site configuration, and all resources. |
| Contributor | Per meeting series; Per project as "Full Access" | Meetings: Can edit fields flagged "editable by contributor" while an event is open. Projects (Full Access): Can submit inspections, upload checklist documents, raise/note concerns. |
| Attendee | Per meeting series; Per project as "Limited Access" | Meetings: Listed on roll call; can mark their own status; read-only for field values unless promoted. Projects (Limited Access): Can submit inspection checks, raise concerns, upload own documents. |
| Standard | Org-wide default | Read-only access to portals they have been granted access to. Cannot create or modify records unless elevated to a resource-specific role above. |
Quick rule
If a user is on the roll call as a Contributor, they can edit fields — but only while the event is still open. Once an admin marks the session complete, all editing locks regardless of role.
Meetings Portal
A structured meeting management system built for shift-based and recurring operational meetings. Each Meeting Series is a standing recurring meeting (e.g. "Morning Tailgate", "Project Kickoff"). Each occurrence is called an Event. Events carry custom data fields, roll call, attachments, weather snapshots, ArcGIS data, and an audit trail.
Permission tiers: Admin — full control · Contributor — edits contributor-flagged fields while event is open · Attendee — roll call participant, read-only field access · Standard — view-only
Series List
Viewing the Series List — All roles
Intent
Gives participants a single landing place to find all their active meetings, with the current period's status visible at a glance.
The portal home shows every meeting series the signed-in user is enrolled in (as admin, contributor, or attendee). Each card displays the series name, optional icon, description, and next scheduled event label. Standard users who have not yet been added to any series will see an empty state with a prompt to contact their meeting organizer. Partner org meetings appear with an org-code badge.
Creating a Meeting Series — Admin only
Intent
Define a standing recurring meeting — its schedule, icon, and initial settings — as a permanent series template from which all events inherit.
Tap + New Meeting Series. Configure:
- Name — The series title, shown on all event headers and email notifications.
- Icon — Pick from 20 industry icons (cranes, rigs, pump icons, etc.) to visually distinguish the series card.
- Description — Optional short description displayed on the series card.
- Frequency — DS/NS (day shift + night shift, 12 hr); Daily; Weekly (pick a day of week + time); Single (one-time event with a specific date).
- Shift times (DS/NS only) — Set the start times for day shift and night shift.
- Virtual meeting URL — A link (e.g. Teams, Zoom) that appears as a "Join" button inside every event.
Groups Tab — Admin only
Intent
Pre-define named rosters (crews, shifts, departments) so a group of people can be added to roll call in one tap rather than individually.
The top-level Groups tab (admin only) manages reusable participant groups. Groups are added to a meeting session's roll call via the + Add Group button inside an event. Each user added via a group is stamped with their group name for display. Individual group membership is managed here — tap a group to see its current members and add or remove them.
Series Detail View
Tap any series card to open its detail view, which contains tabs: Current (opens today's or the current-period's event), History (paginated list of past events), and for admins, Fields and Permissions.
Current / History Tabs — All roles
- Multiple history events can be batch-selected for printing or bulk attachment download.
- The Search bar at the bottom of the series detail lets you search field values, roll call entries, and concerns across all events in this series.
- Batch print renders all selected events to a print-optimized layout with a page break between each — useful for compliance records.
- Batch attachment download bundles all file uploads across selected events into a single zip, named by series, date, and field label.
Fields Tab — Custom Field Editor — Admin only
Intent
Define exactly what information this meeting captures — turning a generic session into a structured data form specific to the meeting's purpose.
Fields are the form items that appear on every event in this series. Each field has:
- Type:
Sectionheader divider ·Textshort text ·Textarealong text (supports rich text) ·Numbernumeric (non-negative) ·Checkboxyes/no ·Dropdownpick from a list - Editable by: Admin only, or Contributor. If "Contributor", signed-in contributors can edit the value during an open event.
- Carry forward: When enabled, the previous event's value auto-populates the field in the new event, with a "carried from [date]" label until it is edited.
- Nested / child fields: Any field can be set as a child of another field for grouping.
- Repeating rows (auto-create): A Number field can be set as an auto-create parent. When its value is n, the system automatically creates n rows of all child fields beneath it — useful for tracking per-pump or per-unit metrics. Maximum 50 rows.
- Enabled/disabled toggle: A field can be temporarily hidden from events without deleting it.
INFO
Fields cannot be reordered across parent boundaries. Use the ▲/▼ arrows to reorder within the same sibling group. To move a field to a different parent, edit the field's "Parent" setting.
Permissions Tab — Contributor Management — Admin only
Intent
Control who can enter data into this series' sessions without granting them full admin rights to the series.
Shows the current-period roll call and the series-level contributor roster. Admins can:
- Add contributors: Selected users are added as standing contributors on this series — they appear on the roll call for every future event automatically.
- Remove contributors: Removes from the standing roster. They will no longer auto-appear on future roll calls but historical events are unaffected.
- Promote/demote in roll call: Within an event's roll call, admins can upgrade an individual attendee to Contributor or downgrade a Contributor to Attendee on a per-event basis.
Running a Session (Event Detail)
Opening an event reveals its full session view: roll call, all custom fields, weather, ArcGIS data, and actions. All changes auto-save on blur — there is no Save button for field values.
The event header shows the series name, event date/period, and status badge: Open (accepting edits) or Completed (locked). Use the ‹ Prev / Next › arrows to move between events in the series history without returning to the series list.
INFO
A calendar export (.ics) button is available in the series detail header. DS/NS series generate two separate .ics files (day shift and night shift). Weekly series anchors the first occurrence to the next matching weekday in Mountain Time.
Roll Call — Admin / Contributor
Intent
Create a live headcount record for each session with attendance status, roles, and company affiliation — forming a defensible record of who was briefed on what.
Each roll call entry has a status: Pending (default), Present, Absent, or Excused. Status changes are debounced — tapping quickly through a long list doesn't fire a network request per tap.
- Adding attendees: Admin can open the Roll Call Manager to add org users, partner org users, or manual entries (for external guests).
- Manual attendees: For people not in the org directory — enter a name and optional company. Editable/removable during an open event.
- Adding a group: Tap + Add Group to bulk-add a pre-defined roster group to this event's roll call in one action.
- Role column: Each entry shows Contributor (can edit fields) or Attendee (read-only). Admin can flip roles inline per event.
Custom Fields — During a Session — Admin / Contributor
Intent
Capture structured meeting data — pre-work readings, observations, counts, decisions — against a consistent template so events are comparable and searchable across time.
Each field auto-saves on focus-leave (blur). Carried-forward values show a grey "from [date]" label until the field is updated for this event. Long-form textarea fields support basic rich text (bold, headings, bullet lists).
- Repeating rows: If a Number field drives repeating children, changing its value adds or removes the matching number of child-field rows. Each row is independently editable.
- Locked state: Once the event is completed, all field inputs become read-only for all roles, including admin.
Field Documents (Reference Attachments) — Admin / Contributor
Intent
Associate supporting files — photos, reports, readings, certificates — with the specific field they relate to, keeping evidence co-located with the data it supports.
Each non-section field has an optional "Attachments" sub-panel. Files are stored against the specific event + field combination. Uploaded files can be viewed in-app (PDF, images) or downloaded. Admins can remove uploaded files.
INFO
Attachments on all selected events in a History batch-select can be bulk-downloaded as a single ZIP via Download Attachments. Files are named: [Series] - [Date] - [Field] - [Title].
Weather — Admin configures, All roles view
Intent
Automatically capture on-site weather conditions at the time of the meeting, reducing the manual burden of recording environmental context and ensuring the record is objective.
When weather is enabled for a series, each event auto-fetches current conditions for the configured latitude/longitude. Displayed data includes temperature, wind speed/direction, humidity, conditions description, and UV index. The weather snapshot is captured at the time the event is first opened and is frozen into the event record when the event is completed.
Weather data is sourced from Open-Meteo. Weather can be turned on/off per series without losing the configuration settings.
ArcGIS Integration Cards
When ArcGIS integrations are enabled for the org and linked to a series, one or more data cards appear on each event. These pull live and historical asset data from the configured ArcGIS feature layers.
ArcGIS Activity Card (Drilling / Assets) — Admin configures, All roles view
Intent
Surface live asset-status information from ArcGIS directly inside the meeting session, so teams can discuss current field conditions without switching apps.
Shows asset features from the linked ArcGIS layer with their current attribute values. Status changes since the last meeting event are highlighted. Admins can configure status categories and custom status groupings. An interactive map view and a detailed well/asset database are available from within the card.
ArcGIS Chart Cards — Admin creates/configures, All roles view
Admin creates Chart Cards from the series Fields tab → ArcGIS Config. Each card selects a field-layer, groups by an attribute, and renders as one of: Bar, Donut, Line, Progress, Stacked Bar, Horizontal Bar, or Multi-line. Charts are snapshotted when the event is completed.
Planned Wells / "Up Next" — Admin & Contributor edit, All roles view
Intent
Maintain a visible queue of upcoming well or work features so field teams always know what's scheduled for the next period without relying on separate planning documents.
When the Planned Wells feature is enabled for a series, a "Up Next" card appears on each event. Admin or contributors can add planned features from the ArcGIS database, add notes, and mark them for removal when work is complete. The system auto-detects likely-completed features and flags them with a "LIKELY DONE" amber label.
Participant Concerns Card — Admin & All roles
Intent
Surface open project concerns that are relevant to meeting participants, so action items raised in the Projects portal are not siloed from operational briefings.
When Participant Actions is enabled for a series (admin toggle), a concerns card appears on each event. It shows open project concerns linked to participants on this series' roll call. Admins can update concern status directly from the meeting view. Concerns are linked to the Projects portal — changes here are reflected there and vice versa.
Completing an Event — Admin only
Intent
Lock the session record so it becomes a permanent, tamper-evident audit entry — and optionally trigger a distribution email so all participants receive a formatted summary.
Tapping Complete Meeting (requires confirmation) locks all field values, freezes the weather snapshot, and writes a completed-at timestamp. If Send Summary Email is enabled for the series, the system dispatches a formatted summary to every roll call member with a "present" or "excused" status.
- A Preview Email option lets admin send a test copy to any address before the real completion.
- Auto-close: Admins can configure an auto-close window (1–23 hours). If the event is not manually completed within that window, the system closes it automatically at the configured hour.
- Once completed, the event is fully locked — no field edits, no roll call changes, no status updates from any role.
Series Settings (Admin)
From the series detail, admins access collapsible settings panels below the Fields list:
| Setting | Description |
|---|---|
| Virtual Meeting URL | Enter a Teams, Zoom, or other video link. Appears as a "Join" button on every event. |
| Weather | Enable / disable weather auto-capture. Configure site coordinates. |
| ArcGIS Integration | Link one or more ArcGIS layer configs to the series. Enables Activity Card, Charts, and Planned Wells. |
| Auto-close Hours | Set how many hours after the period start before the system auto-completes the event. Range: 1–23 hours. |
| Quick Links — Projects | Link specific projects to this series. A "Quick Links" section on each event lets participants jump directly to those projects. |
| Participant Actions | Toggle to show or hide the open project concerns card on every event. |
| Summary Email | Toggle on to send a formatted completion email to all present/excused attendees when the event is marked complete. |
| Delete Series | Permanently deletes the series and all associated events (type-to-confirm). Cannot be undone. |
AI Summary — Admin only
Intent
Automatically synthesise meeting notes from multiple series across a configurable time window into a human-readable digest — eliminating the manual effort of compiling weekly or shift-change summaries.
Tap AI Summary from the portal home. The summary page has two tabs:
- Generate: Select one or more meeting series. Set a date window (last N days, or a custom from/to date range). Optionally add a Prompt Modifier per series to focus the AI on specific aspects (e.g. "Focus on safety observations and action items only"). Tap Generate Summary to run.
- History: Lists previously generated summaries with the series, date range, and a timestamp. Tap to expand and read. Summaries can be deleted.
INFO
Scheduled Summaries: Create a named schedule (daily / weekly / monthly) that auto-generates a summary and optionally emails it. Each schedule stores its own series selection, window, prompt modifiers, and send time.
Projects Portal
A project tracking system for managing site projects from initiation through compliance closure. Each project carries a compliance checklist, concerns tracker, work orders, inspection areas, and a document library.
Permission tiers: Admin — full management · Full Access (Contributor) — inspections, checklist uploads, concerns, documents · Limited Access (Attendee) — submit inspection checks, raise concerns, upload own docs · Standard — view only (no project interaction without access)
Project List
Viewing & Filtering Projects — All roles with project access
The projects list shows all projects the user has access to. A status filter (All / Active / Pending / On Hold / Closed) narrows the list. An Issues Summary panel highlights open concerns across all visible projects. The Org Activity Feed shows recent changes across the org's projects.
Creating a Project — Admin only
Intent
Establish a structured container for a site project, pre-seeding the compliance checklist and creating a central record that spans its full lifecycle.
Tap + New Project. Set: project title, a short project ID code, status, optional description, and location coordinates (for the summary map). The compliance checklist is pre-seeded from the org's checklist template on creation.
Cross-Project Search — All roles with project access
Intent
Find any concern, work order, or inspection note across all your accessible projects without knowing which project it belongs to.
A search bar at the bottom of the projects list searches across all accessible projects simultaneously. Results are grouped by project with a direct "Open →" link. Searches project titles, descriptions, concerns, work orders, and inspection notes.
Project Detail
Project Summary Card — Admin edits, All roles view
Shows project title, ID, status badge, description, and a summary map if coordinates are set. Admins can edit any field. Status changes are tracked in the activity log.
Per-Project Search — All roles with project access
A search bar at the bottom of every project detail view searches within that project only — concerns, concern notes, work orders, inspection area names/descriptions, and inspection check observations.
Compliance Checklist
Checklist Items — Admin (manage, mark complete) · Full Access (upload docs, mark complete) · Limited Access (view only)
Intent
Track the document and approval milestones required before, during, and after a project — ensuring nothing is overlooked and creating a timestamped compliance record.
Each checklist item has a type (e.g. Ground Disturbance, Project Files, CAS Certificate) that determines what actions are available. Items can be marked complete, marked not required (with a type-to-confirm gate), or have files uploaded against them.
WARNING
Marking an item as "Not Required" requires typing a confirmation phrase. This creates an auditable record that the item was intentionally excluded.
Concerns
Raising & Managing Concerns — Admin (full management) · Full Access (raise, note) · Limited Access (raise only)
Intent
Provide a structured channel for any team member to flag issues on a project — ensuring concerns are captured, assigned, and resolved transparently with a full audit trail.
Concerns have a title, description (recommended solution), status (Open / In Progress / Resolved / Closed), and a full note thread. Any Full Access or admin user can add notes. Status changes are admin-only. Each concern links to the Participant Concerns card in any meeting series where Participant Actions is enabled.
Work Orders — Admin creates, All roles view
Intent
Attach specific scoped work items to a project — maintaining a searchable record of what was authorised, when, and against which project.
Each work order has a WO number, description, status, and linked dates. Work orders are searchable via the project search bar.
Inspection Areas & Checks — Admin creates, Full/Limited Access submits
Intent
Define the physical inspection zones on a project and collect recurring check submissions from field teams, building a geospatially-aware inspection history.
Admins create Inspection Areas (named zones). Any Full or Limited Access user can submit an Inspection Check against an area: a form with observations text and optional GPS coordinates. Completed checks appear on the project's inspection map with ArcGIS overlay layers.
Access Management — Admin only
Admins manage project access through two lists: Full Access and Limited Access. Both support org users and partner org users. Users can be promoted (Limited → Full) or demoted (Full → Limited) directly from the access panels.
Dewatering Portal
Tracks dewatering pumps, sump assignments, and periodic sump-check submissions.
| Feature | Access | Description |
|---|---|---|
| Sumps List | View: all · Create/edit: Admin | Active sumps with their assigned pumps and most-recent check date. |
| Submit Sump Check | All roles | Step-by-step guided form: select sump → enter readings → flow-meter rollover check → photo (optional). Drafts auto-save between steps. |
| Pump Database | Admin (manage) · All (view) | Master list of all pumps with asset details, assigned sump, and status. Searchable by all fields including assigned sump. |
| Remove from Sump | Admin only | Detaches a pump from its sump with a confirmation modal. Creates an activity log entry. |
| QR Scan | All roles | Scan a pump's QR code to jump directly to its detail or pre-populate a sump check. |
| Check History | All roles | View all historical sump checks for a given sump, with readings and timestamps. |
WARNING
Draft sump checks are saved per-device and resumed automatically on next visit. If a pump is removed from its sump mid-draft, resuming the draft will detect the mismatch and prompt the user to start fresh.
Wells Portal
Manages groundwater monitoring wells and associated pump/sensor readings. Integrates with ArcGIS for well location and attribute data.
| Feature | Access | Description |
|---|---|---|
| Well List | All roles | List of all monitored wells with current status and last reading date. |
| Well Detail | Admin (manage) · All (view) | Individual well readings history, pump assignments, and ArcGIS attribute data. |
| ArcGIS Map | All roles | Interactive map showing all well locations from the linked ArcGIS layer with attribute popups. |
| Well Pump Database | Admin (manage) · All (view) | Pumps installed in wells, with asset IDs, installation dates, and service records. |
Tools Portal (Radios · Fuel Keys · CAS Units)
A combined asset-tracking portal for radios, fuel keys, and CAS (compressed air systems) units. All three sub-portals share the same access pattern and are searchable from the master asset database.
| Feature | Access | Description |
|---|---|---|
| Radios | Admin (create/edit/assign) · All (view) | Radio inventory with channel assignments, serial numbers, and current holder. Check-out / check-in workflow. |
| Fuel Keys | Admin (manage) · All (view) | Fuel key inventory with asset IDs and holder records. Used to track distribution and returns. |
| CAS Units | Admin (manage) · All (view) | Compressed air units with service records and current location. CAS certs are managed separately in the CAS Certs portal. |
| Master Asset Database | Admin (manage) · All (view) | Unified searchable list of all tools across the org, including partner org assets when sharing is enabled. Org-code badge identifies partner assets. |
| QR Decoder | All roles | Scan any asset QR code to jump directly to its record regardless of asset type. |
| Partner Org Assets | View (when sharing enabled) | When a partnership has asset-sharing enabled, partner org assets appear in your asset lists with an org-code badge. They are read-only. |
Documents Portal
A document library for org-wide reference materials — standards, procedures, policies, forms, and drawings. Documents can be linked into projects and meeting fields.
| Feature | Access | Description |
|---|---|---|
| Browse & Download | All roles | All published documents are visible to standard users. Documents open in the in-app viewer or can be downloaded. |
| Upload & Manage | Admin only | Upload new documents with title, document number, revision, and category. Documents can be edited, revised, and deleted. |
| Link to Projects | Admin only | From within a project detail, admins can link existing documents. Linked documents appear in the project's Linked Documents section. |
| Partner Org Documents | View (when sharing enabled) | Partner org documents shared with your org appear in the list with an org-code badge. They are read-only. |
| Document Currency Notice | All roles | A confirmation modal appears before downloading Standards, Procedures, or Policies, reminding the user to verify they are using the most current version. |
Inspections / Environment Portal
A general-purpose inspection portal for recurring site inspections that are not linked to a specific project. Useful for environmental monitoring, safety walk-arounds, and equipment rounds.
| Feature | Access | Description |
|---|---|---|
| Inspection Types | Admin (define types) | Admins create inspection types with custom field templates. Each type defines what information is collected for that category of inspection. |
| Submit Inspection | All roles | Any user with the Inspections portal can submit a new inspection against a defined type, filling in the template fields and optionally geotagging the location. |
| Inspection History | All roles | View all past inspections, filterable by type and date range. Admins can view all; standard users see their own submissions. |
| Map View | All roles | Geotagged inspections appear on an interactive map. ArcGIS overlay layers are shown if configured for the org. |
Onboarding & Training Portal
Tracks certifications, training completions, and competencies for org members. The GD Competencies section integrates with the Projects portal compliance checklist to gate certain project items on verified training records.
| Feature | Access | Description |
|---|---|---|
| Training Records | View own (Standard) · View all (Admin) | Each user's training history: course names, completion dates, expiry dates. Admins can add, edit, and delete records for any user. |
| GD Competencies | Admin (manage) | Ground Disturbance competency records. These are validated by the Projects checklist before the GD checklist item can be marked complete. |
| Certificate Upload | All roles | Users can upload their own certificates. Admins can review and approve uploaded documents. |
| Expiry Alerts | Admin only | Records approaching or past their expiry date are highlighted in the admin view. Used to prompt renewal before compliance deadlines. |
Remote Locks
Integration with BX Lock smart lock hardware. Allows admins to manage lock inventory, generate access barcodes, and track unlock events — all from within OneSiteKit.
All features are Admin only.
| Feature | Description |
|---|---|
| Lock Inventory | Register and manage physical BX Lock units. Each lock has a hardware ID, name, and location assignment. |
| Barcode Generation | Generate access barcodes (Code128) for a lock. Barcodes can be printed or shared. Each barcode has a configurable access window. |
| Unlock Event Log | Full chronological log of lock unlock events with timestamp and method. Used for site access auditing. |
| Alert Notifications | Configurable alerts for lock events (e.g. unexpected unlock outside permitted hours). Delivered via the notification system. |
FieldMaps (Licensed)
An integration management portal for ArcGIS FieldMaps deployments. Admins configure which ArcGIS layers are exposed for field data collection. Licensing is per-org; access requests go through the Pending Approvals queue.
All features are Admin only.
| Feature | Description |
|---|---|
| Integration Manager | View and manage active ArcGIS FieldMaps integrations. Configure which layers and datasets are accessible to field devices. |
| License Status | View the org's FieldMaps license status, seat count, and request additional seats through the approval flow. |
Remote Sensors (Licensed)
An integration portal for Worldsensing CMT Cloud deployments. Surfaces live geotechnical and environmental sensor readings from the field inside OneSiteKit. Disabled by default — must be enabled per-org from Site Configuration → Portal Toggles (portal_worldsensing).
All configuration is Admin only. Viewing sensor data is available to all roles with the portal enabled.
| Feature | Description |
|---|---|
| Sensor List | All devices registered in your CMT Cloud account with live status (online / warning / offline), latest reading, and battery percentage. |
| Readings Panel | Tap any sensor to see a mini sparkline, min/max/latest summary, and a timestamped list of recent readings. |
| Sensor Types | Temperature (°C), Pressure (kPa), Displacement (mm), Tilt (°), Vibration (mm/s), Water Level (m), Strain (με), Pore Pressure (kPa). |
| Configuration | Enter your CMT Cloud URL and API key. Credentials are stored server-side and never exposed to the browser. Test Connection verifies the link before saving. |
| Proxy architecture | All CMT Cloud API calls are made from the OSK Worker — the frontend only talks to OSK endpoints, never directly to Worldsensing. |
| Alert thresholds | (Planned) Min/max threshold configuration per sensor; OSK cron polls CMT Cloud every 5 minutes and triggers email/SMS alerts on breach. |
CAS Certificates
Tracks Confined Space Entry (CAS) certification records for individuals working in confined spaces. Certificates are submitted, reviewed, and stored here.
| Feature | Access | Description |
|---|---|---|
| Submit New CAS | All roles | Complete the CAS form — entry type, space details, atmosphere readings — and submit for admin review. |
| Certificate History | View own (Standard) · View all (Admin) | All submitted CAS records with status (pending/approved/rejected) and review notes. |
| Import Existing | All roles | Upload an existing CAS certificate document. Admin reviews and approves the import. |
| Admin Review | Admin only | Approve or reject submitted certificates with notes. Approved records are flagged as valid for CAS entry tracking. |
Notepad
A personal rich-text scratch pad. Notes are private to the creator by default and can be shared with specific org members for collaborative editing.
| Feature | Access | Description |
|---|---|---|
| Create / edit notes | All roles | Each note has a title and one or more labeled sections. Content is stored as HTML — bold, italic, underline, strikethrough, bullet lists, numbered lists, and checkboxes are all supported via the formatting toolbar. |
| Sections | All roles | A note can have multiple independently-labeled text sections. Use Add Section to append more; each section can be removed individually when two or more exist. |
| Checkboxes | All roles | Insert tappable checkboxes inside any section. Checking one applies a strikethrough style to its label — useful for inline task lists. |
| Auto-save | All roles | Changes are saved automatically with a short debounce. The last-edited note re-opens on next visit. |
| Share | Note owner | Owner can grant read-write access to specific org members via the Share panel. Shared users can edit the note; only the owner can delete it or change sharing. |
| Delete | Note owner only | Permanently deletes the note and all its shares. |
| Admin toggle | Admin only | Enable or disable Notepad org-wide from Site Configuration → Portal Toggles (portal_notepad). |
QuickTask
A floating compose shortcut available on every screen. The pencil icon pinned above the gear opens a two-step modal for common daily actions without navigating back to the portal.
| Type | What it creates | Key fields |
|---|---|---|
| Action Item | A new concern action on the selected project | Project, title, description (optional), due date (optional), assignees (multi-select, defaults to self) |
| Note | Opens or creates a Notepad note | New blank note or select existing |
| Inspection | Navigates to an inspection portal | Choice of Project / Equipment / Environmental / Wells / Sump |
| Meeting Comment | Appends text to a field in the active meeting event | Series, field, comment text |
The Meeting Comment type is hidden if the user has no meeting series. Action items are routed to a hidden _quick concern category per project and appear in Pending Actions.
Contact List
An org-internal contact directory of key personnel, emergency contacts, and external service providers. Not linked to the user directory — entries are manually maintained.
| Feature | Access | Description |
|---|---|---|
| Browse Contacts | All roles | View all org contacts with role, company, and contact details. |
| Add / Edit Contacts | Admin only | Create and update contact entries. No PII is stored in the user auth system — contacts here are informational only. |
| Categories | Admin only | Contacts can be grouped by category (Emergency, Vendor, Regulator, etc.) to make the directory navigable as it grows. |