Security
Access Control
Role-based access control and permissions in Babelize.
Babelize uses role-based access control (RBAC) to manage who can do what within your projects.
| Role | Description |
|---|
| Owner | Full access, billing, can delete projects |
| Admin | Project management, member invites |
| Editor | Run translations, manage content |
| Viewer | Read-only access |
| Permission | Owner | Admin | Editor | Viewer |
|---|
| View projects | ✓ | ✓ | ✓ | ✓ |
| Create projects | ✓ | ✓ | ✓ | ✗ |
| Delete projects | ✓ | ✓ | ✗ | ✗ |
| Run translations | ✓ | ✓ | ✓ | ✗ |
| Invite members | ✓ | ✓ | ✗ | ✗ |
| Remove members | ✓ | ✓ | ✗ | ✗ |
| Manage billing | ✓ | ✗ | ✗ | ✗ |
| Method | Status |
|---|
| Email OTP | Available |
| GitHub OAuth | Available |
| Google OAuth | Available |
| Property | Value |
|---|
| Duration | 7 days |
| Renewal | On activity |
| Cookie security | HttpOnly, Secure, SameSite |
- Least privilege — assign the minimum role needed
- Review access regularly — remove members who no longer need access
- Use OAuth — reduces password-related risks
