Sharing
Share projects with specific people, teams, or external collaborators.
Default access — what your teammates see based on team and folder rules — covers the common cases. When you need to grant access to someone the defaults don't reach, you reach for Share.
This page covers the share popover, the full share dialog, the share types and access levels you can grant, and how to flip a project between Draft and Published.
The Share Popover
Every project has a Share button. Clicking it opens the compact popover with quick controls:
- Manage access — opens the full share dialog (covered below).
- Share a Link — toggles a read-only public link anyone with the URL can view. Useful for showing work to clients or posting on social.
Public links are independent of workspace membership — if Share a Link is on, anyone with the URL gets a view-only copy. Turn it off to revoke.
The Full Share Dialog
Manage access opens the full share dialog. It has two tabs: Internal for people inside the workspace, and External for people outside it.
Internal
The Internal tab targets people and teams in your workspace. Pick a person or team from the search field, choose an access level (View, Comment, or Edit), and the share is added.
You can:
- Share with an individual workspace Member.
- Share with a whole Team — every team member gets the chosen access level.
- Expand a team share to see each member's effective access.
- Remove a share with the X on its row.
Sharing with someone who already has access
If you try to share with a person who already has access through a team or folder default — say they're in the team that owns the folder — the dialog shows their existing access alongside an Elevate to Edit (or Comment) button. Elevation creates an explicit share that overrides the inherited level upward. There's no way to elevate downward; sharing only adds access.
External
The External tab invites people who aren't in your workspace by email. Fuser sends them a link they can use to view, comment on, or edit the project — no workspace membership required.
External email shares only work if your workspace allows them. The toggle lives at Workspace Settings → Sharing Policies → Allow External Email Sharing. When it's off, the External tab is still visible but new email invites are rejected — turn the policy on to grant them.
Share Types
You can grant access to four kinds of grantee:
- User share — a specific workspace member.
- Team share — every member of a team.
- Email share — someone outside the workspace (only if external sharing is on).
- Folder share — applied to a whole folder. The share extends to every project inside the folder via inheritance.
Folder shares are added from the folder's own context menu, not the project's share dialog. Use them when you want to grant a guest access to a whole batch of work at once.
Access Levels
Three access levels exist when sharing:
- View — read the project and see comments.
- Comment — view, plus create and resolve comments. Comment access is share-only — you can't set a folder to default-Comment.
- Edit — comment, plus modify or delete the project.
Shares only add access — they cannot reduce it. If a folder gives someone Edit by default, sharing them View on a project inside doesn't downgrade them. To restrict access, change the folder default or move the project.
Project Visibility — Draft vs. Published
Independent of sharing, every project has a visibility setting that decides whether it's openly visible to its surrounding context.
- Draft — only the creator and workspace Admins can see the project. Teammates need an explicit share, even if they could otherwise see the folder.
- Published — visible to everyone who can reach the project's location, at the access level the folder or workspace root defines.
You change visibility two ways:
- From the project itself — open the share popover and use the visibility toggle at the top.
- From a project card — right-click any project on the home page and pick a visibility option from the context menu.
Only the project's creator or a workspace Admin can change visibility.
Re-drafting removes others' access
Switching a Published project back to Draft removes everyone else's access immediately — including, in some cases, your own. If you weren't the original creator, you'll lose access too unless you have an explicit share. Make sure you have an explicit Edit share on the project before flipping it back.