Plan Availability | Team, Professional, Enterprise and Signature |
Permissions | Solution Managers and Administrator role users |
Related Reading |
SmartSuite supports Folder Permissions, allowing Solution Managers and above to control access to folders within the Table. In this guide, we’ll walk you through the steps to configure folder visibility settings, manage permissions, and ensure secure collaboration.
Accessing Folder Settings
Navigate to the Folder
Log in to SmartSuite and select the desired folder.
Open Folder Settings
Configuring Folder Settings
1. Change Folder Name
2. Folder Visibility Settings
Everyone: The folder is visible to all users (default). All users with access to the table and its contents can see the folder and its Views.
Selected Members: The folder is visible only to users selected by the Solution Manager.
3. Selected Members Setting
This advanced setting allows Solution Managers to fine-tune folder visibility with three sub-options:
Members: Individual users who should have access to the folder.
Teams: Specific teams requiring access.
Permission Roles: Roles (e.g., “Editors,” “Viewers”) that define access rights.
Combining Selections
Selections within each of the three groups can be combined. For example:
Folder Visibility: Visible to Member A, Team B, and Editors.
Note: All options are connected using the AND operator.
Applying Permissions
Members Controls
Lists individual users who can access the folder.
Click the blue plus (+) icon to select Members.
Teams Control
Lists all teams with access to the folder.
Click the blue plus (+) icon to select Teams.
Permission Roles Control
Select one or more roles to allow access. Members with the selected roles can view the folder and its Views.
Important Notes
This control displays all permission roles, even if none are currently assigned within the table. For example, even if everyone in the table has Full Access, the Assignee role will still be listed.
Folder permissions control access to the views in a particular folder, but do not modify individual Member or Team permission for the Table, records or fields.
Practical Scenarios and Use Cases
1. Confidential HR Views
Scenario: The HR department wants to store views that include sensitive employee records and restrict access to only HR personnel.
Solution: Create an "HR Records" folder and limit visibility to HR team members only, ensuring that only HR team members see views that contain confidential data. Note that the confidential data itself must be protected by Solution, Table and field-level permissions.
2. Project-Specific Access Control
Scenario: A company launches a new product and wants to provide easy access to project-related data to key team members only.
Solution: Set up a private folder for the product launch, assign specific permissions, and control who can view the project-specific views.
3. Cross-Functional Teams
Scenario: Engineers, designers, and product managers collaborate on a new feature.
Solution: Create a "Feature Development" folder, ensuring all roles have access to shared tasks and communication channels.
Note: Remember to save your changes after configuring folder settings!