Team & project access
Each StringJet project is a shared workspace with its own members, roles, and seat limit from the owner’s plan. Invite people by email, assign a role, and keep production changes in the hands of trusted developers or owners — especially for OTA publishes.
Invite by email
From the Contributors tab, add a user with their address and starting role. Invitations align with your remaining seats; if you hit the cap, upgrade on pricing or free a seat.
Roles
Roles map to how people work day to day:
- Member — collaborate on strings without full publishing privileges.
- Developer — can participate in engineering workflows; owners and developers can publish or manage OTA bundles per product rules.
- Translator — focused on locale content and review.
- Designer — aligns with design-led review alongside comments.
- Owner — project owner retains billing and destructive actions such as delete.
Seats per project
Plans cap how many distinct members each owned project can include. End users who only consume strings in your mobile app via OTA are not seats — only people signing into StringJet count. Compare tiers on pricing.
Project info & SDK identifiers
The Project info tab exposes the public project id, SDK token, languages, enabled platforms, and OTA platform subset. Copy fields safely into your apps and CI; rotate tokens from the app if needed. Deep integration steps live on Add the SDK.