📄️ Overview
The goal of the Resgrid project is to have a complete, all-in-one solution that organizations of any size can utilize to manage the intersection of dispatches, personnel and resources. Being a complete solution does not mean it's 'best of breed' for the individual modules (i.e. shifts), as such we want to target a minimum level of functionality for each module and a level of customization to make Resgrid malleable out of the box.
📄️ Sizing Guidelines
Usage is dynamic, so we cannot make hard recommendations on hardware or hardware configuration (i.e. CPU count, RAM, etc) but below are just some general guidelines on how we approach the systems design of the system based on how many active elements there are in the system.
📄️ Docker
Docker Container Images
📄️ Auditing
Resgrid has 3 levels of auditing in the system.
📄️ Localization
Resgrid's website and applications can support multiple languages.
📄️ Workflow Template Variables
This page provides the complete reference for all template variables available in Resgrid Workflows. Variables use Scriban syntax: {{ variable.property }}.
📄️ Feature Flags & Module Gates
Some Resgrid modules are behind feature flags so they can be rolled out gradually. On the hosted service Resgrid staff switch them on; on a self-hosted installation the operator does it with the tools console. Flags are stored in the database (FeatureFlags, FeatureFlagOverrides, FeatureFlagTargetingRules, FeatureFlagPrerequisites), cached, and evaluated per department: a department override wins over a percentage rollout and targeting rules, which win over the global default.