Add Zulivio - #1017
Open
Raktim94 wants to merge 7 commits into
Open
Conversation
Workforce-ops CRM: lead pipeline board, custom fields on CSV lead imports, helpdesk, and employee accounts with a forced password-change gate after an admin reset. 1.6.1: fixes a Helpdesk page crash when myRuns/definitions didn't resolve to an array.
Permanent employee delete for separated employees with no history to lose, a dashboard quick-access shortcut row, a quick note button on lead board cards, and a copy-to-clipboard button for the lead phone number.
…ange) This PR branch's 1.5.0 entry only summarized the S3/Helmet/email-uniqueness part of that release. Brings in the rest that shipped in the same commit: the assignment/employee-number race fix, the auth guard going global by default, and the role-hierarchy consolidation.
…ll-leads danger zone
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New app: Zulivio
Free, open-source (AGPL-3.0), self-hostable CRM and workforce operations
platform: role-based employee management (add/remove with auto-generated
credentials), work assignment tracking with outcomes, an explicit
attendance state machine (shift/break/logout with a full audit trail), a
PDF knowledge base with acknowledgement tracking, a Sales CRM (leads,
pipelines, opportunities, territory/capacity-based routing, rep-level
forecasting), a Sales Head / RBAC layer with scope-resolution and
dashboard drill-down, quality audit/workflow/helpdesk tooling, a master
dashboard with live analytics, and CSV/Google Sheets import-export. Runs
entirely on the user's own hardware — no subscription, no data leaving
their server.
ghcr.io/raktim94/zulivio-{backend,web}:1.7.0, public, multi-arch (amd64/arm64)What's new since this PR opened (now at 1.7.0)
lead/assignment/attendance/etc. history to lose — otherwise the app
explains exactly what's blocking it. Also fixes a gap where a
SUSPENDED/ON_LEAVE employee had no way to be separated at all.
log a note without opening the lead.
workspace page (the board cards already had it).
category, outreach angle, etc.) into a custom-fields bag instead of
dropping them, so any export shape can be imported without a schema
change.
employee's password.
cards.
How this was validated
docker compose config -qpasses on the app's compose file.x-casaosfields cross-checked against the currentdocs/specs/compose-and-x-casaos.md(id format, required/recommended fields,categoryenum, quotedport_map) — unchanged by this bump, onlyversion/update_at/release_notes/image tags moved.linux/amd64+linux/arm64) and pullable at the pinned1.7.0tag viadocker buildx imagetools inspect.nest build(not justtsc --noEmit, which has previously diverged from it on this repo) and the full e2e suite (148/148) pass. Frontend: realnext buildpasses../scripts/build_dist.shlocally (nopipin this environment) — relying on this PR's own CI (validator.yml) for the full build check.Boot-test from the 1.5.0 bump (unchanged startup path)
Booted the compose file locally end-to-end with a throwaway
AppIDand scratch bind mounts (no/DATApaths touched): Postgres came up healthy, the backend started clean with zero manually-set env vars, andFIELD_ENCRYPTION_KEYwas confirmed to auto-generate and persist to the/data/secretsvolume on first use — no manual key setup required.