Sloth-ninja keeps Clio open while firms lock down custom connectors

The fork draws a cleaner line between a firm-approved practice-management tool and member-added integrations.

integrationworkflow

For organization users, Clio remains accessible even where firm policy prevents members from adding their own connectors. That means a restriction on custom integrations no longer accidentally shuts the door on the practice-management connection the firm may rely on.

Clio access: organization users can reach the Clio option, or see plainly when it has not been configured.
Custom connector controls: firms can still keep the gallery of member-added connectors unavailable under their policy.
Clearer navigation: the Connectors area stays visible for organization users, rather than disappearing because custom additions are restricted.

The change is narrow, but it makes the product's governance model easier to understand: approved firm tooling is not the same thing as open-ended integrations.

So what Firms using Clio should care because they can tighten integration policy without making their core practice-management connection harder for lawyers and staff to find.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`e2573b2e`	Exempt Clio card from the memberMcpConnectors policy	sloth-ninja	2026-08-03	↗ GitHub
commit body Owner decision (03/08): the "Members may add custom connectors" policy governs custom MCP servers only; the Practice management - Clio card must be reachable for all org users regardless. - connectors/page.tsx: the personalConnectorsBlocked early-return now renders <ClioConnectorCard /> above the neutral FirmManagedCard (which stays for the MCP gallery); neutral copy narrowed to "Custom connectors". - account/layout.tsx: Connectors tab always visible (drop the personalConnectorsBlocked filter branch + its now-unused import). - BUILD_LOG: new entry (layout decision (a) recorded); the #64 open owner decision marked TAKEN (exempt). Frontend only; backend untouched. tsc clean; eslint clean on changed files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`3684498b`	BUILD_LOG: restore the orphaned PR 3 heading, normalise entry separator	sloth-ninja	2026-08-03	↗ GitHub
commit body The exemption entry's heading had displaced #64's "Clio connector PR 3: frontend" heading, orphaning its Scope block. Reinstate the PR 3 heading above that block and normalise to a single `---` + blank line between the two entries. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1073.md from inside the repo you want the changes in.

⬇ Download capture-thread-1073.md