Projects & Teams

How LocaleLens organizes translations and enables team collaboration

What is a Project?

A project is a container for your translations. Each project contains translation keys, multiple locales, team members, and API keys.

Think of a project as an isolated workspace for one app, client, or environment.

Each Project Contains

How Projects Isolate Data

Projects are completely isolated from each other. Translation keys, locales, and team access never cross project boundaries.

This design prevents accidental data leaks, simplifies access control, and scales cleanly from solo developers to teams.

Project-Specific

Account-Level (Shared)

Note: Usage limits (Free/Pro) are applied at the account level and shared across all projects.

Team Collaboration

Invite team members to collaborate on specific projects. Each member has a role that determines their permissions.

Owner

Full control

Admin

Manage team & content

Translator

Edit content only

Viewer

View only

Permissions by Role

Up to 3 members (account-wide)

Up to 50 members (account-wide)

You can upgrade anytime as your team grows.

Common Project Setups

Setup 1: One App = One Project

Most common setup for solo developers and small teams

Create one project for your application. All languages and translations live in the same project. Your entire team has access.

Project: "Marketing Website"
├── en (English)
├── es (Spanish)
├── fr (French)
└── Team: 5 members

Setup 2: Production / Staging Split

Separate environments for testing

Use separate projects for production and staging. Test translation changes before deploying. Different API keys prevent accidents.

Project: "App - Production"
└── API Key: prod_xxxx

Project: "App - Staging"
└── API Key: staging_xxxx

Setup 3: Managing Multiple Clients

For agencies and freelancers — clean separation of client work

Create one project per client. Different team members per project. Client data stays completely separate.

Project: "Client A - E-commerce"
└── Team: Agency devs + Client A team

Project: "Client B - SaaS Dashboard"
└── Team: Agency devs + Client B team

Best Practices

✓One project per application (unless you need environment splits)
✓Use descriptive project names (e.g., "Marketing Website" not "Project 1")
✓Invite team members with the minimum role they need
✓Keep API keys secure — they're project-specific and grant access to all translations

Requires a LocaleLens account