Does SeaTable offer ways of restricting seeing sensitive columns for the majority of team members?
I have a table “customers” where the default/complete view includes all kinds of sensitive/identifiable (name, email, dob) columns, as well as many non-sensitive columns. I’d like to be able to hide the sensitive columns from the majority of my team, but I do want everyone to have access to the non-sensitive columns.
What I’ve tried is to create a view “deidentified” where I hide the afffected columns, but how do I:
limit acesss to the default view to only those needing access?
ensure the “deidentified” view (visible to all) can’t be modified by individual users in some way to expose the sensitive columns?
I’ve read all the help pages on views and team aministration but can’t fgure out how to set this up (or whether it is possible at all). An entirely different route with the same functionality would be fine too of course.
To restrict users from viewing sensitive columns in a SeaTable base using the app feature, you can utilize the column permissions and page authorizations functionalities available in SeaTable. Here’s a step-by-step guide based on the reference materials:
Access Page Settings: In the SeaTable app, navigate to the table page where you want to restrict access. Click on the cogwheel icon in the navigation bar to access the page settings.
Set Column Permissions: In the page settings, you can configure individual column permissions. You have the option to mark specific columns as “read-only” or “hidden.”
Read-Only Columns: If you set a column to read-only, users will be able to see the data but cannot edit it. These columns will be highlighted in gray and marked with a lock symbol, indicating that they are not editable by users [Reference 1].
Hidden Columns: To completely restrict visibility, you can hide columns. Simply toggle the slider for the columns you want to hide. Users will not see these columns at all, ensuring sensitive information is not accessible [Reference 1].
Page Authorizations: You can also manage who can view or edit the entire page. In the page authorizations settings, specify which user groups have access to view or modify the data on that page. This allows for granular control over who can see what data [Reference 2].
Preset Filters: To further refine what data users can see, you can apply preset filters. This means that even if a user has access to a page, they will only see the data that meets the filter criteria you set. This is particularly useful for ensuring that sensitive information is not displayed inadvertently [Reference 1].
No Inheritance of Base Settings: It’s important to note that hidden and locked columns in the underlying base do not automatically apply to the app. Therefore, you must set these permissions specifically within the app settings to ensure they take effect [Reference 1].
Testing Permissions: After setting up the permissions, it’s advisable to test the app with a user account that has restricted access to ensure that the settings work as intended. This helps confirm that sensitive columns are indeed hidden or read-only as required.
By following these steps, you can effectively restrict users from viewing sensitive columns in your SeaTable base, ensuring that data privacy and security are maintained. For more detailed information on managing permissions and settings, refer to the SeaTable documentation [Reference 1][Reference 2].
