← Documentation

Teams & Brand Workspaces

A team is a self-contained brand workspace: its own passes, credit wallet, brand defaults, and signing certificate. Switch between them like switching brands.

The model: one team per brand

Everything in Pass Studio runs in a context — your personal account, or one of your teams. The Team Switcher in the top navigation (next to the notification bell) selects the context, and everything follows it: the dashboard shows that team's passes, new passes are created in the team, credits are drawn from the team's wallet, and new designs start from the team's brand defaults.

That makes a team the natural unit for a brand. An agency runs one team per client; a multi-brand merchant runs one team per banner. Members see and edit everything in the teams they belong to — and nothing in each other's personal contexts.

Typical uses

  • An agency manages five client brands — five teams, each with the client's own colors, logo, wallet, and certificate. Designers switch brands from the top bar.
  • A franchise operator gives each location's manager access to the shared brand team while keeping billing centralized in the team wallet.
  • A freelancer builds a client's loyalty program in a dedicated team, then invites the client as a member for handover — no shared logins.

Creating a team and inviting members

  1. Go to Settings → Teams & Collaborators → New team. You become its owner and it becomes your active context.
  2. Invite members by email from the team card. Invitees get an email link (or copy the invite link and share it directly). Teams hold up to 10 members.
  3. Roles: Owners manage billing, brand defaults, the team certificate, renaming, and membership. Members create and edit passes, run campaigns, and invite collaborators.

Working in team context

  • Passes — passes created while the team is active belong to the team, visible and editable by every member. Cloning a team pass stays in the team.
  • Billing — all credit deductions in team context (pass creation, issuance, pushes, campaigns) draw from the team's wallet, never a member's personal balance. Teams have their own plan and payment method, managed from the team's billing page by owners.
  • Brand defaults — new passes start with the team's stored brand kit (below), or the branding of the team's most recently saved pass when no kit is set.
  • Certificate — passes in the team are signed with the team's own white-label certificate when one is set up (below).

Brand defaults

Owners can pin a brand kit on the team card (Settings → Teams → expand the team → Brand defaults): background, text and label colors, logo and icon, and the organization name shown on the pass. Every new pass created in the team starts from the kit, so a brand's passes stay consistent no matter which member creates them — and experimenting on one pass never drifts the defaults.

When no kit is set, new passes inherit from the team's most recently saved pass — convenient for a single brand, less predictable for agencies. Pin the kit once per client and forget it.

Per-team white-label certificate

White-label signing is per-context too. With a team active in the Team Switcher, Settings → White-label Passes manages the team's certificate (owner-only, requires the team to be on a Growth or Pro plan): either automatic setup under Pass Studio's Apple developer account, or upload the brand's own .p12. Every pass in the team is then signed under that brand's dedicated Pass Type ID — regardless of which member created the pass.

Resolution order for a team pass: team certificate → the pass creator's personal certificate → the shared Pass Studio certificate. See Apple Certificates for what white-label changes on the pass itself.

Typical uses

  • An agency uploads each client's own Apple certificate to that client's team — every wallet pass shows the client as the issuer, with the agency invisible.
  • A brand starts on the shared Pass Studio certificate, then upgrades the team to Growth and enables white-label — new pass downloads pick up the brand identity automatically.

Switching and leaving

  • Switch context any time from the Team Switcher or from Settings → Teams. Your personal context is always available — personal passes are never visible to teammates.
  • Members can leave a team from the team card; owners can remove members. Removing a member revokes access immediately — passes stay with the team.
  • Deleting a team (owner-only) reverts its passes to the members who created them.

Questions? Reach us at info@idardirect.com.