Roles Overview
Written By Nabil
Last updated About 1 month ago
Why it’s useful
Clear access levels prevent accidents like clients editing internal notes or contributors accessing sensitive workspace projects. BugSmash controls permissions through different invite paths, keeping collaboration open but access tightly scoped.
How it works
Access Type → Access Summary
Admin → Admin has almost all the same privileges as owner including billing
Member → Member can join workspace via invite and will have access to all your workspace projects
Collaborator → Collaborators can create/upload project in your workspace but cannot view other projects.
Guest Reviewer→ External users invited to provide feedback without needing External users invited to provide feedback without needing full access. Limited to commenting and reviewing.
Example
> The agency invites internal designers as Members for full workspace collaboration, QA testers as Workspace Guests so they can upload builds without seeing other projects, and clients as Guests through the project Share menu to collect feedback without risking accidental changes.
Tips
- Invite long-term teammates as Members from Workspace → Members.
- Use Workspace Guests for contributors who need upload access but limited visibility.
- Add clients as Guests from inside each project so their access stays scoped to only what they should review.
- Periodically review invited users to maintain strong security.