Permissions Per Collection

By default, all inventory collections in Labguru are visible to every member who has Inventory access in their role. Permissions Per Collection lets account admins go further — restricting specific collections to only the members or teams who need them.

This is useful for labs that want to reduce clutter, protect sensitive materials, or separate inventory across teams or clients.

Who can configure collection permissions?

• Account Admins — can manage permissions for any collection
• Inventory Admins — can manage permissions for collections they administer

System and Inventory Admins always have full access to all collections and are not affected by collection-level permissions.

How to configure collection permissions.

1. On the Account Settings page, select the Collections tab.
2. Find the collection you want to manage and click Customize.
3. Scroll down to the Collection Visibility section.
4. Choose one of the following:

Make the collection public (default)
All members with Inventory role access can see this collection. This is the default for all collections.

Restrict the collection
Uncheck the public checkbox, then use the member and team selector to choose who should have access.

5. Click Save.

💡 Tip: Granting access to a team is the most efficient way to manage access for a group — all current and future team members inherit the collection access automatically.

What happens after you restrict a collection

For members without access:

• The collection disappears from their Inventory menu entirely.
• Attempting to navigate to it directly returns an authorization error.
• They cannot add items from this collection to sample elements or sample baskets in experiments.

For members with access:

• Nothing changes. They see and interact with the collection per their existing role permissions.

For admins:

• Account Admins, Inventory Admins, PIs, and System Admins always retain full access regardless of the access list.

Permission reference

Note: Collection-level permissions control which collections a member can see. What they can do inside a collection (view, edit, delete) is still determined by their role. This feature does not change role-based privileges.

Use cases