Release Notes
Per Party Access Levels
Shared Spaces now support per-party access levels, so a resource owner can set what each organization in a Space can view, edit, or run.
What's New
If you are the owner of a resource in Harvey — such as a vault, playbook, agents, thread, or review table — you now have the ability to set organization-specific access levels when you share that resource in a Shared Space.
Per-party access levels allow you to:
- Set a separate access level (view, edit, run, or no access) for each party in a Shared Space before sharing your resource
- Use View as Party to see a Space exactly as a specific party experiences it
- Use Preview (previously View as) to check the collaborator or guest experience before anyone is invited
Note: Your existing access configurations will carry over automatically and will remain as is. Space admins, connection admins, or workspace admins still must approve any external resource sharing or access level changes.
Why It Matters
Previously, all parties in a Shared Space were granted the same access level when a resource was shared. Per-party access levels allow you to adjust access levels for each party based on their role, providing you with more control over who can view, edit, or access resources within the space.
How to Use
Refer to Shared Spaces Overview for instructions on setting per-party access levels.
FAQs
Q: Will my existing Shared Space configurations change?
No. Every existing workspace keeps the same access it has today. This update only adds the ability to set more granular, per-party access levels going forward.
Q: Who can change access levels for a resource?
The resource owner can set per-party access levels, but Space admins, connection admins, or workspace admins must still approve any external resource sharing or access level changes.