API Keys Can Now Be Scoped to Multiple Spaces
🎯 What is it?
You can now configure a single API key to work across multiple spaces in your workspace, instead of being limited to one space at a time. This gives you more granular control over how integrations access your Dust environment.
💡 Why is it useful?
Previously, if you wanted an integration to access multiple spaces, you had two options: either give it workspace-wide access (too permissive) or create separate API keys for each space (too complex). This new capability follows the principle of least privilege—you can grant access to exactly the spaces an integration needs, nothing more and nothing less.
⚙️ How does it work?
When creating or editing an API key in the admin UI, you can now select multiple spaces that the key should have access to. The permission resolution has been updated to handle this multi-space access smoothly.
✨ Concrete Use Cases
Here's how you could use it:
Export shared agents: You have an agent shared across 3 different team spaces (Sales, Marketing, Customer Success). You can now create one API key scoped to these 3 spaces to export or sync that agent's data, instead of managing 3 separate keys.
Controlled cross-team integration: Your data pipeline needs to access specific spaces (Finance and Legal) but not others. You can create a single API key with access to only those two spaces, maintaining security while simplifying key management.
📈 Benefits for you
-
Better security: Apply least-privilege principles without operational complexity
-
Simpler management: One key for multiple spaces instead of juggling multiple keys
-
Unlock new workflows: Run integrations across controlled sets of spaces that weren't practical before
🚀 How to access it?
This feature is already live for all workspace admins. When you create or manage API keys in your workspace admin panel, you'll see the option to select multiple spaces. All existing API keys have been automatically migrated, so nothing changes unless you want to adjust the configuration.