Enabling Table-Specific Access Permissions for Users

David S. · 2025-01-22 00:37:33.377893+00

Hi I was wondering if there's a way to allow enable access permissions so that certain users can only access certain tables. Is that a thing?

Enabling Table-Specific Access Permissions for Users | Clay

12 comments

· Sorted by Oldest

Channeled
APP
·
·
In Clay, user access is managed through workspace roles. There are two main roles available: 1. User Role: • Can edit workspace resources (tables, workflows, and integrations) • Has limited access focused on editing workspace resources 2. Admin Role: • Can edit all workspace resources • Has ability to invite and remove team members • Can assign or update roles between User and AdminCurrently, there isn't a way to restrict access to specific tables - users with either role can access all workspace resources. The main difference is that Admins have additional team management capabilities. Source: Adding workspace members | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
David S.
·
·
I have certain tables that should only be viewed by specific users on my team. I'm wondering if there is a way to controlling access at a table level to who can view.
LuisArturo
·
·
Hey there David thanks for reaching out, currently we do not have a way to control viewing/edit access for Clay tables, although his something the team has looking into implementing, however there is no current ETA for when this could happen
David S.
·
·
Thank you for letting me know. As an alternative, Is there a way to have an account with multiple work spaces where some team can access and others can't? Just trying to figure out the best way to set things up.
David S.
·
·
To play this out, in my mind, if I could have 2 work spaces. Then I can keep the sensitive stuff in one with limited access, and then have the non-sensitive the other. Is that something that exists? Or is the only alternative to have two accounts for my company?
Bo (.
·
·
Yes, you can set up multiple workspaces with different access levels, but each workspace would need its own plan to maintain the same feature access. I totally get the need to separate sensitive and non-sensitive data - it's a common requirement. While having two accounts would work right now, I wanted to let you know we're actually on fast-track development of better workspace controls. Can't give an exact date, but it's a priority feature coming soon that might better fit your needs.
David S.
·
·
Thanks Bo (. in the case that you want/need beta users for this workspace controls, we'd love to be involved as soon as possible :)
Bo (.
·
·
Will do! :)
Channeled
APP
·
·
Hi David S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback David S.!
Channeled
APP
·
·
Thank you so much for sharing your feedback David S.!

Channeled
APP
·
·
In Clay, user access is managed through workspace roles. There are two main roles available: 1. User Role: • Can edit workspace resources (tables, workflows, and integrations) • Has limited access focused on editing workspace resources 2. Admin Role: • Can edit all workspace resources • Has ability to invite and remove team members • Can assign or update roles between User and AdminCurrently, there isn't a way to restrict access to specific tables - users with either role can access all workspace resources. The main difference is that Admins have additional team management capabilities. Source: Adding workspace members | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
David S.
·
·
I have certain tables that should only be viewed by specific users on my team. I'm wondering if there is a way to controlling access at a table level to who can view.
LuisArturo
·
·
Hey there David thanks for reaching out, currently we do not have a way to control viewing/edit access for Clay tables, although his something the team has looking into implementing, however there is no current ETA for when this could happen
David S.
·
·
Thank you for letting me know. As an alternative, Is there a way to have an account with multiple work spaces where some team can access and others can't? Just trying to figure out the best way to set things up.
David S.
·
·
To play this out, in my mind, if I could have 2 work spaces. Then I can keep the sensitive stuff in one with limited access, and then have the non-sensitive the other. Is that something that exists? Or is the only alternative to have two accounts for my company?
Bo (.
·
·
Yes, you can set up multiple workspaces with different access levels, but each workspace would need its own plan to maintain the same feature access. I totally get the need to separate sensitive and non-sensitive data - it's a common requirement. While having two accounts would work right now, I wanted to let you know we're actually on fast-track development of better workspace controls. Can't give an exact date, but it's a priority feature coming soon that might better fit your needs.
David S.
·
·
Thanks Bo (. in the case that you want/need beta users for this workspace controls, we'd love to be involved as soon as possible :)
Bo (.
·
·
Will do! :)
Channeled
APP
·
·
Hi David S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback David S.!
Channeled
APP
·
·
Thank you so much for sharing your feedback David S.!