Roles and Permissions
Roles and permissions control what actions users can perform in Smart-1 Cloud.
They provide a structured way to manage access across the Check Point Portal and SmartConsole, ensuring that administrators and operational teams have only the permissions required for their responsibilities.
Smart-1 Cloud uses Specific Service Roles, which apply only to Smart-1 Cloud within the Check Point Portal. These roles control access to Smart-1 Cloud management features and operations.
Types of Smart-1 Cloud Service Roles
-
Predefined Service Roles - For more information, see Predefined Service Roles
-
These roles are included with Smart-1 Cloud and correspond to fixed permission profiles in Web, Streamed, or installed SmartConsole.
-
They provide baseline access levels, such as full administrative permissions, approving permissions, or read‑only viewing.
-
Predefined roles cannot be modified.
-
-
Custom Permission Profiles (Custom Service Roles) - For more information, see Custom Roles and Permissions
-
Administrators can create custom permission profiles in any version of SmartConsole (Web, Streamed, or installed).
-
After publishing and refreshing the page in the Check Point Portal, these profiles appear as Smart-1 Cloud Specific Service Roles.
-
Custom profiles allow administrators to create finely tuned permission sets for specialized operational needs.
-
|
|
Note - A user can have only one assigned Smart-1 Cloud service role. |
Where Smart‑1 Cloud Roles Are Created and Assigned
-
Predefined service roles are available by default in the Check Point Portal.
-
Custom permission profiles are created in Web, Streamed, or installed SmartConsole and synchronized to the portal.
-
All Smart-1 Cloud service roles - both predefined and custom - are assigned in the Check Point Portal under: Users → Specific Service Roles → Smart-1 Cloud.
For more information about Global Roles and Specific Service Roles, see the Check Point Portal Administration Guide.
Roles Purpose
A structured permissions model helps organizations:
-
Enforce the principle of least privilege
-
Reduce the risk of unauthorized changes
-
Maintain consistent access policies across teams and regions
-
Support auditing and compliance requirements
-
Delegate tasks without exposing sensitive configuration areas