Managing Access for Sales Teams in Clay's Production Workspace

Aaron J. · 2025-10-24 21:32:51.085441+00

I'm running into an issue where my sales team wants access to Clay to 'Learn as they go' but our production workspace is connected into critical infrastructure. I dont see any way to create partial/limited access to a workspace, am I missing something, or are separate workspaces the best answer here. And if separate workspaces are the answer, is there a way to split our subscription credits in some way?

Managing Access for Sales Teams in Clay's Production Workspace | Clay

7 comments

· Sorted by Oldest

Clay Support
APP
·
·
You have two options:
Option 1: Workbook-level restrictions (Enterprise only)
If you're on an Enterprise plan, you can restrict edit access to specific workbooks. Set critical workbooks to "Workspace admins and specific collaborators" so your sales team can view them but not edit. [1]
Note: There's no table-level view restriction—members can see all tables/workbooks once invited.
Option 2: Separate workspaces
Your sales team can create their own trial accounts (separate workspaces) to learn independently. However, credits cannot be split between workspaces—each workspace has its own subscription and credit allocation. [2]
Are you currently on an Enterprise plan?
Aaron J.
·
·
No we are not on an enterprise level plan.
Clay Support
APP
·
·
Got it. Since you're not on Enterprise, separate workspaces are your best option. Your sales team can create their own trial accounts to learn Clay independently—each person gets their own workspace with trial credits. [1]
Credits can't be split between workspaces, so each workspace has its own subscription and credit allocation. [2] This keeps your production workspace completely isolated from their learning environment.
Are you thinking your sales team would eventually need access to your production workspace once they're trained up?
Aaron J.
·
·
No, because it would give them admin-level access to systems we do not currently allow them to access as admins (salesforce for example)
Clay Support
APP
·
·
That makes sense—keeping them in separate workspaces is the right call then. Each team member can create their own trial account to learn Clay independently without any risk to your production setup or connected systems. [1]
Each trial comes with its own credits (1,000 credits to start), so they can explore freely without affecting your production workspace's credit allocation. [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you need any more help with setting up separate workspaces or managing credits, please let me know. Would you like to share more about what you're trying to achieve or any other concerns you have?

Clay Support
APP
·
·
You have two options:
Option 1: Workbook-level restrictions (Enterprise only)
If you're on an Enterprise plan, you can restrict edit access to specific workbooks. Set critical workbooks to "Workspace admins and specific collaborators" so your sales team can view them but not edit. [1]
Note: There's no table-level view restriction—members can see all tables/workbooks once invited.
Option 2: Separate workspaces
Your sales team can create their own trial accounts (separate workspaces) to learn independently. However, credits cannot be split between workspaces—each workspace has its own subscription and credit allocation. [2]
Are you currently on an Enterprise plan?
Aaron J.
·
·
No we are not on an enterprise level plan.
Clay Support
APP
·
·
Got it. Since you're not on Enterprise, separate workspaces are your best option. Your sales team can create their own trial accounts to learn Clay independently—each person gets their own workspace with trial credits. [1]
Credits can't be split between workspaces, so each workspace has its own subscription and credit allocation. [2] This keeps your production workspace completely isolated from their learning environment.
Are you thinking your sales team would eventually need access to your production workspace once they're trained up?
Aaron J.
·
·
No, because it would give them admin-level access to systems we do not currently allow them to access as admins (salesforce for example)
Clay Support
APP
·
·
That makes sense—keeping them in separate workspaces is the right call then. Each team member can create their own trial account to learn Clay independently without any risk to your production setup or connected systems. [1]
Each trial comes with its own credits (1,000 credits to start), so they can explore freely without affecting your production workspace's credit allocation. [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you need any more help with setting up separate workspaces or managing credits, please let me know. Would you like to share more about what you're trying to achieve or any other concerns you have?