Roles & Permissions
Stringhive has two levels of access control: team-level and hive-level. Most small teams won't need to think about this much, but it's useful when you have translators who should only work on specific Hives, or when you want to prevent accidental changes.
Team-level roles
Every team member has a team-level role:
| Role | What they can do |
|---|---|
| Owner | Everything, including billing and deleting the team |
| Admin | Everything except billing. Can manage members, hives, settings. |
| Member | Access Hives they've been given access to, translate strings |
When you invite someone to your team, they start as a Member.
Hive-level roles
Within a Hive, you can assign a more specific role:
| Role | What they can do |
|---|---|
| Admin | Full control over the Hive: settings, members, import/export, approve translations |
| Translator | Translate and save strings, but can't change Hive settings or approve |
| Viewer | Read-only access |
A team Admin has implicit admin access to all Hives. A team Member only has access to Hives where they've been explicitly assigned a role.
Inviting members
From your team settings, click Invite member and enter their email. They'll get an invite link. Once they accept, they appear in your member list and you can assign Hive-level roles.
Removing members
In team settings, find the member and click Remove. Their translations and activity history stay in the system. Only their access is revoked.