User Roles and Permissions in Socket

Overview

Every user of Socket is associated with an email and may be part of one or more GitHub organizations. The organizations a user is associated with can be viewed in the dashboard. Adding a GitHub organization to a user is done by installing the Socket for GitHub application on a repository in that GitHub organization. Users can be invited to an organization by using the People tab in that organization's dashboard. Pending and existing users can be managed from the People tab as well.

User Roles and Permissions

Permissions Matrix

Note: Members can only read API tokens with the visibility set to "organization members".

Owner

• Permissions: Full access to all repositories and the team, including billing, adding, or removing members.
• Responsibilities: Manages the entire organization and has the highest level of control.

Administrator

• Permissions: Access to all repositories and the team, including billing, adding, or removing members.
• Responsibilities: Helps manage the organization and maintain its settings.

Member

• Permissions: Add and edit specific repositories.
• Responsibilities: Collaborates on specific repositories assigned by the Admin or Owner.

Contributor

• Permissions: Limited access to contribute code but no team-level access or permissions to change repo-level settings.
• Responsibilities: Contributes code to repositories but cannot manage settings or team members.

Managing Users

• Inviting Users: Admins and Owners can invite new users by sending invitations via the People tab.
• Pending Invitations: View and manage pending user invitations in the People tab.
• Existing Users: Manage roles and permissions of existing users from the People tab.

People Tab

[]
The People tab allows you to manage users, view pending invitations, and adjust user roles.

Users and Seats

Inviting a user does not consume a seat. Socket bills per dev seat, and only active committers (people who trigger a full scan through a commit or an API request) count against your seat total. Users who only sign in to view the dashboard, read alerts, or triage findings are free, no matter how many you invite.

If you need more billable dev seats, an Owner or Admin can raise the seat count from Settings Billing using the Change seats option. See Billing for the full walkthrough, seat limits, and how the prorated charge works.

SSO and Default Member Role

• SSO Configuration: Enable SAML Single Sign-On for organization members via an Identity Provider.
• Default Member Role: Set the default role (Member or Contributor) for new members signing in via SSO in the Settings tab.

Settings Tab

[]
The Settings tab provides options for configuring SSO and setting default member roles for new sign-ins.

By understanding and utilizing these roles and permissions, organizations can effectively manage their teams and maintain a secure and collaborative environment using Socket.