Feature
One shared screenshot library for your whole team
Keep team captures in one workspace with pooled storage and member roles. Owners and admins can see all team captures; members can see teammate captures when the sharing setting is enabled.
Step 01
One shared library
The shared team library lets members see captures added by the team rather than keeping every screenshot locked to the person who took it. Instead of forwarding images one by one, the team works from a single collection that everyone with access can see.
- Members can see teammate captures when shared viewing is enabled.
- Access depends on each person's role and the shared-viewing setting.
Step 02
Roles and access
Team has three roles. The Owner can invite admins, change roles, and manage billing and settings. Admins can invite members, manage settings, and see all captures. Members see teammate captures when Let members view teammate captures is on.
- Owner: invite admins, change roles, manage billing and settings.
- Admin: invite members, manage settings, see all captures.
- Member: sees teammate captures when Let members view teammate captures is on.
This separation keeps administrative control with owners and admins while members get the day-to-day benefit of the shared library. Roles are assigned when you invite someone and can be changed by the owner later.
Step 03
Shared storage per seat
Each paid seat adds 20 GB of storage, and that storage is pooled across the team rather than fenced off per person. A member who captures heavily and one who captures rarely draw from the same shared pool, so capacity follows actual usage.
- 20 GB per paid seat, pooled and shared across the team.
- Pro, by contrast, gives each user an individual 10 GB.
- Capacity scales with the number of paid seats.
Step 04
Inviting your team
You add people by sending an email invite and assigning a role at the same time, so each person joins with the right level of access. Owners can invite admins, and both owners and admins can invite members.
- Email invites with a role assigned on the way in.
- Pending invites can be revoked.
- Invites expire rather than staying open forever.
Invites are not permanent commitments. A pending invite can be revoked before it is accepted, and invites expire, so a stale invitation does not stay open indefinitely.
Step 05
Central billing and seats
The owner manages the seat count and billing for the whole team from one account, so there are no individual subscriptions to reconcile. Seats are the paid seats you are billed for, and they set both the storage pool and how many people can join.
- Owner manages seat count and billing centrally.
- Seats equal the paid seats on the account.
- Open seats = paid seats minus active members and pending invites.
Open seats are simply paid seats minus the people already using them: paid seats less active members and pending invites. When open seats run out, the owner adds more seats to invite the next person.
Step 06
Walk through the Team controls with a test fixture
The linked proof uses the real Team page rendered with explicitly fictional owner, admin and member fixtures. It is a test UI, not a customer account, and it does not demonstrate a server role change or a sent invitation.
An owner can choose the teammate-viewing setting, inspect pending invitations and change member roles. Admins can invite members and manage access settings; only owners can invite admins and change roles. Members can view teammate captures only when Let members view teammate captures is on. Owners and admins retain access to all Team captures.
Step 07
Check both access paths and the storage pool
Let members view teammate captures governs whether a member can read captures made by teammates. Allow members to create public links is a separate switch. When it is off, members cannot create links from Team captures or Personal captures covered by that Team; owners and admins can still create links.
The paid Team plan adds 20 GiB per paid seat to one storage pool. The pool counts the Team workspace and eligible Team-covered free Personal workspaces, so it is not unlimited storage and not a separate 20 GiB allowance for every folder. The member count plus pending invitations uses seats.
Step 08
Agree on the handoff before adding an image
A shared library is more useful when each screenshot has a clear task, neutral title and responsible reviewer. Use the review worksheet to record what was removed, who needs access and when that access can end.
Team membership and a public share link are different access paths. Review both when closing a sensitive handoff.
FAQ
Common questions.
Short answers about capture, privacy, sharing, and billing.