Restrict Access to a Fibery Space
Use the Space Access page to grant the minimum role each collaborator needs, then inspect effective access. Space grants can include data as well as Views and documents.
Before you start: Use an account permitted to manage Space access. Excluding Space data from a grant or hiding data from Admins requires Pro or Enterprise.
Worked example: A roadmap reviewer should read a Product Space but should not reconfigure its databases. Give that colleague Viewer rather than Architect, then check whether group membership grants more.
Step-by-step guide
Inspect existing access
Expand the Space in the sidebar and open Access. Identify individual, group and Admin grants before changing anything.
Apply a suitable role
Add the intended person, choose Viewer for read access, and click Invite. Use stronger roles only for an explicit editing or configuration task.
Remove unintended grants
Review the existing rows for people and groups outside the audience. Consider other valid access paths before concluding a removed row fully revokes access.
Audit the result
Click Shared with … users in the top right. Expand the reviewer to inspect the grants that combine into their effective access.
Validate with the reviewer
Have them open a normal View and a source record. Confirm they can read the intended content and cannot perform the restricted configuration task.
Common mistakes
Assuming Admins disappear from the Space
Admins retain Architect access to structure. On supported plans, excluding data is a separate mechanism, with Space-level content caveats.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.