The Permissions tab on a game lets you grant specific Collaborators access to just that one game. Used right, this is how you bring an external artist or a publisher into one game without exposing your whole portfolio.

For the strategic context (Member vs Collaborator, when to scope), see Set yourself up for success: collaborator permissions. This page is the mechanics.

What this page helps you do

Grant view or edit access to a specific Collaborator on this game.
Change someone's per-game permission later.
Revoke access cleanly when a project ends.

Before you start

The person needs to be in your team workspace as a Collaborator before you can grant per-game access. Invite them first, see Invite and manage team members.
Members and Admins see all games in your workspace by default; per-game permissions don't apply to them. You'd only use this tab for Collaborators.

Open the Permissions tab

On the game's page, click Permissions. You see a list of Collaborators currently granted access to this game.

If no one's been granted access, the list is empty.

Grant access

Click Add collaborator (or Grant access). A dropdown lists the Collaborators in your team. Pick one.

Then pick a permission level:

View: they can see the game and its details, but can't edit.
Edit: they can update the game's content (descriptions, components, media, rules, etc.) just like a Member.

Save. The Collaborator can now see this game next time they sign in.

You can grant access to as many Collaborators as you need; each can have a different permission level on the same game.

Change someone's level

In the Permissions list, click the level next to a Collaborator and pick a new one. Save.

The change takes effect immediately. They don't get a notification, let them know if it matters.

Revoke access

In the Collaborator's row, pick Remove (or Revoke access). Confirm.

The Collaborator can no longer see this game. Anything they created (comments, uploads, rules edits) stays attached to the game, only their ongoing access is removed.

If you re-grant access later, they pick up where they left off.

What "view" actually means

A view-only Collaborator on this game can:

See all tabs of the game page.
Read components, media, rules, notes, versions.
See playtests, pitches, and sell sheets attached to this game.
Read comments on tasks attached to projects linked to this game.

They cannot:

Edit any field.
Add components, media, rules, notes.
Create playtests or pitches on this game.
See other games in your team.

What "edit" means

Edit access is essentially Member access scoped to one game. The Collaborator can do everything a Member could on this game, add and remove content, create playtests, log pitches, run the project board.

They still can't:

See other games (unless individually granted).
Manage team-level settings, billing, or members.
Delete the game itself.

Tips & common questions

My freelancer doesn't see the game. Two things to check: are they in your team as a Collaborator (not blocked or unaccepted)? And is their email confirmed? If both look good and they still don't see it, ask them to sign out and back in.

Can I scope a Collaborator to multiple games? Yes, repeat the grant on each game. Each game's permissions are independent.

What's the difference between this and just making them a Member? A Member sees everything in the team. A Collaborator with per-game grants sees only what you've granted. If they need to see more than 3-4 specific games, Member is usually simpler. See Set yourself up for success: collaborator permissions for the strategy.

Can publishers be Collaborators? Yes. For an active publisher relationship, granting Collaborator view-only on one specific game lets them follow progress without seeing everything else you're working on.

Does view-only block them from downloading attachments? View-only blocks editing, not downloading. If you've shared a sell sheet or rules PDF on the game, they can download. To restrict downloads, keep the asset private (don't toggle it public), see Game media.