houseassassin/twenty
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(billing) - fix orphaned stripe subs (#20814)

Browse Source 
Fix sentry issues
https://twenty-v7.sentry.io/issues/7203797925/?environment=prod&project=4507072499810304&query=is%3Aunresolved%20assigned%3Ame&referrer=issue-stream

An orphaned sub is a not "canceled" stripe sub with no matching
workspace

- Clean all orphaned sub (script not included in this PR)
- Ensure to soft delete > cancel stripe sub > check for not active sub >
hard delete in every workspace deletion flow

Bonus : 
- Remove dead code
- Update doc on RLS (to improve AI chat knowledge)
This commit is contained in:
Etienne
2026-05-21 19:02:54 +02:00
committed by GitHub
parent 3c91f3f276
commit 0edd8d400c
15 changed files with 109 additions and 256 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/twenty-docs/user-guide/permissions-access/capabilities/permissions.mdx
+15
View File
@@ -95,6 +95,21 @@ Click **+ Add rule** and select an object to create an exception.
| Opportunities → disable "See Records" | Intern cannot see the Opportunities object at all |
| People → enable "Edit Records" | Intern can edit People records (but not other objects) |
### Row-Level Permissions
<Note>
Row-level permissions are a **Premium feature** available on the **Organization** plan (Cloud and Self-Hosted).
</Note>
Row-level permissions let you restrict which individual records a role can see or edit, based on dynamic criteria. Unlike object permissions (which apply to an entire object type), row-level permissions evaluate each record independently.
**Example use cases:**
- Sales reps can only see their own opportunities
- Managers can see all records in their region
- Support agents can only view tickets assigned to them
To configure row-level permissions, open a role, navigate to the **Objects** tab, and use the **Row-Level** section to define filter conditions for a specific object.
### Field Permissions
Within each object-level rule, you can go further and configure **field-level permissions** to control access to specific fields.
packages/twenty-docs/user-guide/permissions-access/how-tos/permissions-faq.mdx
+1 -1
View File
@@ -60,7 +60,7 @@ For fields:
</Accordion>
<Accordion title="Can I restrict access to specific records (row-level permissions)?">
Row-level permissions will be available on the **Organization** plan by Q1 2026. This allows you to restrict access to specific records based on criteria (e.g., only see your own opportunities).
Row-level permissions are available on the **Organization** plan. This allows you to restrict access to specific records based on criteria (e.g., only see your own opportunities).
</Accordion>
<Accordion title="How do I make a field read-only for certain users?">