3 Commits

Author	SHA1	Message	Date
Paul Rastoin	ea3c5d2d45	Migrate role and role target to v2 (#16009) ... # Introduction close https://github.com/twentyhq/core-team-issues/issues/1930 close https://github.com/twentyhq/core-team-issues/issues/1929 Migrating role and roleTarget entities to the v2 core engine, allowing v2 caching leverage and allow migrating agent to v2 that needs role target in prior After agent we should be able to pass twenty standard app totally though workspace migration ## Role target assignation Please note that role target have 3 creation entrypoints: - Agent - User workspace - ApiKey Refactored all 3 of them to pass through a new role-target.service.ts that consumes the v2 under the hood. --------- Co-authored-by: Weiko <corentin@twenty.com>	2025-11-28 17:06:11 +00:00
Marie	2877b28afb	[permissions] Enable permissionsV2 in seeds (#12623) ... In this PR - enable permissions V2 in seeds - remove permission V2 toggle in tests	2025-06-17 09:56:11 +00:00
Marie	cdc4badec3	[permissions] Writing permission does not go without reading permission (#12573) ... Closes https://github.com/twentyhq/core-team-issues/issues/868 We should not allow to grant any writing permission (update, soft delete, delete) on an object or at role-level without the reading permission at the same level. This has been implemented in the front-end at role level, and is yet to be done at object level (@Weiko)	2025-06-16 10:04:38 +00:00