5 Commits

Include renames

Author	SHA1	Message	Date
admin	e7f0070e84	fix(restore): återställ default branch-filer som raderades av docs-publiceringen (7e33543) ... Återställer 6136 filer från 7e33543^. Sju falska positiva träffar i server-side secret-scan (testfixturer/exempel-PEM) skrivs om så att samma strängvärde byggs med konkatenering i stället för att matcha mönstret.	2026-11-10 09:37:22 +01:00
admin	2bee8eb778	docs(production): standardiserad produktionsberedskap och gap-analys ... Lägger docs/production-readiness.md och siax/production-gaps.json enligt SIAX Master Definition of Done. Underlag: git-, kod- och live-evidens 2026-11-11. Nivån är evidensbaserad, inte ett leveransgodkännande.	2026-11-10 09:15:21 +01:00
3 people	c31933b15b	perf(api): write routes stop re-resolving the active company (#1928) ... * perf(api): write routes stop re-resolving the active company withRouteContext resolves the active company (one resolve_active_company RPC, ~40 ms p50 on prod) and then, for the 256 routes that pass requireWrite: true, called requireWritePermission(), which resolved it a second time before its role select. Two sequential round trips repeating work the wrapper had just done, on every mutating request. requireWritePermission() and getCompanyRole() now accept an optional `known` context; the wrapper passes { companyId }, so the helper goes straight to the membership select. Callers that pass nothing behave exactly as before, and the shared selectRole() keeps both helpers on the same query. The role is still looked up, never trusted from the caller. Tests: known companyId skips resolution, known role skips the select, a known viewer is still 403, a known company without a membership row is still 403, legacy calls unchanged; new lib/api/__tests__/with-route- context.test.ts pins that the wrapper resolves the company exactly once, hands it to the guard, never calls the guard on read routes, passes the guard's 403 through with a request id, and emits Server-Timing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * test(customers): viewer gate expects the wrapper to hand over the resolved company Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>	2026-08-26 13:55:48 +02:00
Mattsson	cd376e1cad	feat: implement viewer role permissions for bank transaction imports and connections (#234)	2026-04-13 19:43:28 +02:00
Mattsson	a1a816b4a5	Delete features (#218) ... * Implement company and account deletion features - Add event types for company and account deletion to CoreEvent. - Enhance Supabase middleware to handle company context resolution and cookie management for archived companies. - Create API routes for deleting accounts and companies, including necessary validations and event emissions. - Implement tests for account and company deletion endpoints to ensure proper functionality and error handling. - Add retention notice component to inform users about bookkeeping data retention during destructive actions. - Create database migrations to support soft deletion of companies and anonymization of user accounts, ensuring compliance with retention laws. * feat: enhance account deletion process and update user notifications * Add service client for onboarding completion check and update escape hatch visibility * Enhance invite flow and email handling for company members * Refactor company context and RLS policies for active company isolation - Update `switchCompany` to remove unnecessary revalidation as client handles navigation. - Revise `getActiveCompanyId` to prioritize `user_preferences` and validate against non-archived memberships. - Modify `setActiveCompany` to ensure `user_preferences` is the authoritative source while maintaining cookie compatibility. - Enhance middleware to resolve active company using `user_preferences` and fallback to first non-archived membership. - Introduce new API route `/api/company/current` to fetch the active company ID for cross-tab synchronization. - Implement `CompanyTabSync` component for real-time active company enforcement across tabs. - Create migration for RLS policies to enforce single-active-company isolation using `current_active_company_id()`. * feat: implement viewer role enforcement for write permissions - Added `useCanWrite` hook to determine if the current user has write permissions based on their role in the active company. - Updated various components (JournalEntryForm, CustomerForm, DeadlineForm, etc.) to disable write actions and show a lock icon with a tooltip for users without write permissions. - Introduced `requireWritePermission` function to enforce write permissions at the API level, returning a 403 response for viewers. - Created tests to verify the behavior of the viewer role and write permissions. - Added database migration to enforce read-only access for viewers at the database level.	2026-04-11 17:06:32 +02:00