docs: align RACI overview with actual Kosli roles

implementation_guide/phase_1/roles_and_responsibilities/app_developers.md

@@ -73,7 +73,7 @@ To perform the responsibilities described above, users in this role typically ne
 
 Developers typically need to report attestations and manage flows for their applications. The Member role enables this. Some developers may only need visibility into deployments and compliance status, making the Reader role sufficient.
 
-Learn more about [Kosli user roles and permissions]().
+Learn more about [Kosli user roles and permissions](/administration/managing_users/roles_in_kosli).
 
 ## Where to start
 - [**Getting Started**](): Follow this if you're curious about how Kosli works behind the scenes

implementation_guide/phase_1/roles_and_responsibilities/overview.md

@@ -68,11 +68,12 @@ The RACI model helps teams and stakeholders know who to talk to, who drives a de
 
 ## Connecting Responsibilities to Permissions
 
-The RACI matrix above describes responsibilities during Kosli implementation. To perform these responsibilities, users need appropriate Kosli user roles (Admin, Member, or Reader) assigned in the platform.
+The RACI matrix above describes responsibilities during Kosli implementation. To perform these responsibilities, users need appropriate Kosli user roles (Admin, Member, Snapshotter, or Reader) assigned in the platform.
 
 Kosli user roles control what actions someone can perform in the Kosli system:
 - **Admin**: Full control, including user management and organization settings
 - **Member**: Can create and modify resources, manage service accounts, and configure integrations
+- **Snapshotter**: Can report environment snapshots and manage service accounts, with read-only access to other resources
 - **Reader**: Read-only access to view data and compliance status
 
-For guidance on which Kosli user role to assign based on organizational responsibilities, see Roles in Kosli.
+For guidance on which Kosli user role to assign based on organizational responsibilities, see [Roles in Kosli](/administration/managing_users/roles_in_kosli) and [Mapping users to roles](/administration/managing_users/mapping_users_to_roles).

implementation_guide/phase_1/roles_and_responsibilities/platform_engineers.md

@@ -80,7 +80,7 @@ To perform the responsibilities described above, users in this role typically ne
 
 Platform engineers need to set up flows, manage service accounts, configure integrations, and implement Kosli across teams. The Member role provides these capabilities. Lead platform engineers who manage the overall organizational setup may require Admin access to manage users and organization settings.
 
-Learn more about [Kosli user roles and permissions]().
+Learn more about [Kosli user roles and permissions](/administration/managing_users/roles_in_kosli).
 
 ## Where to start