District Options
A handful of district-wide settings decide how FiscFlow behaves for everyone - whether approvals are required, how requisition numbers are assigned, and how strictly submission windows are enforced. Get these right before go-live.
District Options aren't cosmetic. Several of them turn entire approval workflows on or off, and two of them seed defaults onto every record created afterward. Decide your policy first, then create your classifications and positions.
Where to find them
Open Setup → District. There is a single District record for your organization. Edit it, change what you need, and Save.
Changes take effect immediately on save - no need for anyone to log out and back in. FiscFlow refreshes the cached settings the moment the District record is saved.
Settings that change how FiscFlow works
These four settings (plus the current fiscal year) are the ones that alter functionality. Each is described with what happens when it's on versus off.
Require Personnel Requisition Approval
The single most impactful setting. It decides whether Personnel Requisitions (PRs) must go through an approval workflow at all.
| State | What happens |
|---|---|
| Off default |
Every PR is treated as already approved. No PR submission or approval step is enforced, and the PR-approval fields are hidden on classifications. Use this if your district doesn't route PRs for sign-off in FiscFlow. |
| On | PRs whose classification requires approval are not approved until their PR submission is run all the way through the workflow to finalization. This unlocks the PR approval process, PR "lock-in," and the adjust/resubmit actions. |
This option sets the default for the Requires Personnel Requisition Approval checkbox on each Employee Assignment Classification you create afterward. Turning it on later won't retroactively change classifications that already exist - set it first, or adjust each classification by hand. Whether a specific PR needs approval is ultimately the classification's setting and this district switch both being on.
Require Employee Assignment Approval
Decides whether a new position (Employee Assignment) must be approved before it counts.
| State | What happens |
|---|---|
| On default |
A new assignment is created unapproved and must be approved by someone holding an approver role (a role with Can Approve Employee Assignments). Until then it's blocked from downstream use, and trying to approve without permission is refused. |
| Off | A new assignment auto-approves the moment it's saved - FiscFlow stamps it approved and adds an "Auto Approval" note. Positions become usable immediately with no approval step. |
Auto-Generate Personnel Requisition Numbers
Decides whether PR numbers are assigned by the system or typed in by a person.
| State | What happens |
|---|---|
| On | FiscFlow assigns the PR number automatically (shown as a padded number like
PR000123). The manual PR-number field is disabled and
not required. |
| Off default |
The user must enter a PR number manually. The field is editable and required - a PR can't be saved without one. |
Submission Window Flexibility (days)
A district-wide grace period, in days, for submitting slightly late. If a submission's window closed up to this many days ago, it can still be submitted.
- Default is 0 - no grace; once a window closes, it's closed.
- Set it to, say,
5to allow submitting up to five days after a window ends.
The grace period only extends unrestricted submission windows. A window configured with restricted submission dates gets no grace, no matter what this value is set to. Use restricted dates when a deadline is truly hard.
Current Fiscal Year
Points FiscFlow at your district's active fiscal year. You can only choose a fiscal year marked active. This value is used as the default year for new records and as the anchor for year-based filtering throughout the app.
If the Current Fiscal Year is missing or points at the wrong year, new records default to the wrong year and year-based views filter incorrectly. Update it as part of your annual rollover.
District identity (appears on reports)
These fields identify your district but do not change any behavior. They're used to fill in report titles and headers - for example, the Personnel Services Board Report.
| Field | Used for |
|---|---|
| Name | District name printed on reports and titles. |
| Address | Contact block on documents. |
| Phone Number | Contact block on documents. |
| Website | Reference only. |
| Tag Line | Optional subtitle for reports/headers. |
System Options
A separate Setup → System Options record holds organization-wide technical settings - mainly the calendar/scheduler display and integration endpoints. These are typically set once during setup.
| Setting | Purpose |
|---|---|
| Default Security Role | The role applied by default when security roles are merged. |
| Visible Scheduler Start / End Time | The hours shown on calendar/scheduler views (0-24). |
| Working Start / End Time | The highlighted "working hours" band on the scheduler (0-24). |
| Scheduler Time Scale | Grid granularity: Hour, 30, 15, 10, 6, or 5 minutes. |
| Security service URL | Endpoint for the automated security-role merge, if your district uses it. |
The start time must be less than or equal to the end time for both the visible-scheduler range and the working-hours range, or the record won't save.
Before go-live: a settings checklist
- Current Fiscal Year - set to the active year.
- Require Personnel Requisition Approval - set your policy first; it seeds every classification you create afterward.
- Require Employee Assignment Approval - confirm whether positions need manual approval (on) or should auto-approve (off).
- Auto-Generate PR Numbers - decide system-assigned vs. manual PR numbers.
- Submission Window Flexibility - set the grace days (0 for none).
- District identity - Name/Address for report headers.