Team & Permissions

PlayKit supports collaboration at two levels: game members (per-game roles) and organizations (workspace-wide access). All collaboration is managed in the PlayKit Dashboard.

Game Members

Each game has its own member list. You invite collaborators to a specific game and assign them a role that controls what they can do.

Roles

• Owner — Full control. Can change settings, manage tokens, invite and remove members, and delete the game. Every game must have at least one owner.
• Editor — Can configure the game and manage tokens, but cannot manage members or delete the game.
• Viewer — Read-only access. Can view settings, usage, and analytics but cannot make changes.

Inviting Members

From a game's Members page in the dashboard:

1. Click Invite Member
2. Select the user to invite
3. Assign a role (Owner, Editor, or Viewer)
4. Confirm

The member gains access immediately — there is no pending-invitation step. You can change a member's role or remove them at any time from the same page.

The last remaining owner of a game cannot be demoted or removed — this ensures every game always has at least one owner.

Organizations

Organizations let a team share a workspace and a single wallet across multiple games. Organization membership is managed through your identity provider; within PlayKit there are two organization roles:

• Admin — Full access to every game in the organization, regardless of game-level membership. Can manage the organization's shared wallet and settings.
• Member — Can create games and fully manage the games they create, but cannot edit games owned by others unless explicitly added as a game member. Can view the org wallet balance but not manage it.

Personal Workspace

If you are not part of an organization, you work in a personal workspace. You are the sole administrator of all games you create, and all billing uses your personal wallet.

How the Two Levels Interact

• An organization admin can manage any game in the org, even without an explicit game membership row.
• An organization member has access only to games they own or have been added to as a game member.
• Game roles (Owner/Editor/Viewer) apply on top of organization membership — use them to give a specific collaborator scoped access to a single game without granting org-wide admin rights.

Audit Log

Member management actions — invitations, role changes, and removals — are recorded in the game's audit log, so you can review who changed access and when.

Next Steps

• Core Concepts — Game IDs, tokens, and credits
• Credits & Costs — How organization and player wallets work