Control de acceso¶
Distinto en la versión 3.0: Hasta Weblate 3.0, el sistema de privilegios se basaba en Django, pero ahora se ha construido específicamente para Weblate. Si utiliza una versión antigua, consulte la documentación que corresponda a esa versión, ya que la información que aquí se ofrece no será relevante.
Weblate incluye un sistema de privilegios detallado que permite asignar permisos de usuario en toda la instalación o en un ámbito limitado.
The permission system based on groups and roles, where roles define a set of permissions, and groups assign them to users and translations, see Users, roles, groups and permissions for more details.
After installation a default set of groups is created, and you can use those to assign users roles for the whole instance (see Default groups and roles). Additionally when Control de acceso por proyecto is turned on, you can assign users to specific translation projects. More fine-grained configuration can be achieved using Custom access control
Common setups¶
Bloquear Weblate¶
To completely lock down your Weblate installation, you can use
LOGIN_REQUIRED_URLS to force users to sign in and
REGISTRATION_OPEN to prevent new registrations.
Permisos para todo el sitio¶
To manage permissions for a whole instance, just add users to Users (this is done by default using the Asignaciones de grupo automático), Reviewers and Managers groups. Keep all projects configured as Public (see Control de acceso por proyecto).
Permisos por proyecto¶
Set your projects to Protected or Private, and manage users per project in the Weblate interface.
Añadir permisos a idiomas, componentes o proyectos¶
You can additionally grant permissions to any user based on project, component or language set. To achieve this, create a new group (e.g. Czech translators) and configure it for a given resource. Any assigned permissions will be granted to members of that group for selected resources.
This will work just fine without additional setup, if using per project permissions. For permissions on the whole instance, you will probably also want to remove these permissions from the Users group, or change automatic assignment of all users to that group (see Asignaciones de grupo automático).
Ver también
Control de acceso por proyecto¶
Nota
By enabling ACL, all users are prohibited from accessing anything within a given project, unless you add the permissions for them to do just that.
You can limit user’s access to individual projects. This feature is turned on by Access control in the configuration of each respective project. This automatically creates several groups for this project, see Grupos predefinidos.
The following choices exist for Access control:
- Público
Públicamente visible y traducibles
- Protegido
Publicly visible, but translatable only for selected users
- Privado
Visible and translatable only for selected users
- Personalizado
Weblate no gestiona los usuarios; vea Custom access control.
To allow access to this project, you have to add the privilege either directly to the given user, or group of users in the Django admin interface, or by using user management on the project page, as described in Managing per project access control.
Nota
Aunque se haya activado ACL, determinados datos de resumen sobre su proyecto estarán disponibles:
Estadísticas de toda la instalación, incluidos recuentos para todos los proyectos.
Language summary for the whole instance, including counts for all projects.
Asignaciones de grupo automático¶
You can set up Weblate to automatically add users to groups based on their e-mail addresses. This automatic assignment happens only at the time of account creation.
This can be set up in the Django admin interface for each group (in the Authentication section).
Nota
The automatic group assignment for the Users and Viewers groups will
always be created by Weblate upon migrations, in case you want to turn it
off, simply set the regular expression to ^$, which will never match.
Users, roles, groups and permissions¶
Los modelos de autenticación consisten de varios objetos:
- Permission
Individual permissions defined by Weblate. You can not assign individual permissions, this can only be done through assignment of roles.
- Role
Role defines a set of permissions. This allows reuse of these sets in several places, and makes the administration easier.
- User
Los usuarios pueden ser miembros de varios grupos.
- Group
Groups connect roles, users and authentication objects (projects, languages and component lists).
Comprobación de permisos¶
Whenever a permission is checked to decide whether one is able to perform a given action, the check is carried out according to scope, and the following checks are performed in the order:
Component list is matched against component or project.
Components are matched against component or project.
Projects are matched against project.
Como podrá apreciar, otorgar acceso a un componente también da automáticamente al usuario acceso al proyecto contenedor.
Nota
Only the first rule will be used. So if you set all of Component list, Components and Project, only Component list will be applied.
An additional step is performed if checking permission for the translation:
4. Languages are matched against the scope of translations if set, if not set, this does not match any language.
Consejo
You can use Language selection or Project selection to automate inclusion of all languages or projects.
Comprobar el acceso a un proyecto¶
A user has to be a member of a group linked to the project or any component inside it. Only membership is enough, no specific permissions are needed to access a project (this is used in the default Viewers group, see Default groups and roles).
Comprobar el acceso a un componente¶
A user can access the unrestricted component once he can access the containing project. With enabled Acceso restringido the access to the component requires explicit permission to the component (or containing component list).
Gestionar usuarios y grupos¶
All users and groups can be managed using the Django admin interface,
available under /admin/ URL.
Managing per project access control¶
Nota
This feature only works for ACL controlled projects, see Control de acceso por proyecto.
Users with the Can manage ACL rules for a project privilege (see Control de acceso) can also manage users in projects with access control turned on through the project page. The interface allows you to:
Añadir usuarios existentes al proyecto
Invitar usuarios nuevos al proyecto
Cambiar los permisos de los usuarios
Revocar el acceso de los usuarios
The user management is available in the Manage menu of a project:
Ver también
Grupos predefinidos¶
Weblate comes with a predefined set of groups for a project, wherefrom you can assign users.
-
Administration Has all permissions available in the project.
-
Glossary Can manage glossary (add or remove entries, or upload).
-
Languages Can manage translated languages - add or remove translations.
-
Screenshots Can manage screenshots - add or remove them, and associate them to source strings.
-
Template Can edit translation templates in Componentes monolingües and source string info.
-
Translate Can translate the project, and upload translations made offline.
-
VCS Can manage VCS and access the exported repository.
-
Review Can approve translations during review.
-
Billing Can access billing info (see Facturación).
Custom access control¶
By choosing Custom as Access control, Weblate will stop
managing access for a given project, and all users and groups can be managed using the Django
admin interface. This can be used to define more complex access control, or
set up a shared access policy for all projects in a single Weblate instance. If you
want to turn this on for all projects by default, please configure the
DEFAULT_ACCESS_CONTROL.
Advertencia
By turning this on, Weblate will remove all Control de acceso por proyecto it has created for this project. If you are doing this without admin permission from the instance, you will instantly lose your access to manage the project.
Default groups and roles¶
Lista de privilegios¶
- Billing (see Facturación)
View billing info [Administration, Billing]
- Cambios
Descargar cambios [Administración]
- Comentarios
Post comment [Administration, Edit source, Power user, Review strings, Translate]
Eliminar comentario [Administración]
- Componente
Editar configuración de componentes [Administración]
Lock component, preventing it from being translated [Administration]
- Glosario
Añadir entrada de glosario [Administración, Gestionar glosario, Usuario avanzado]
Editar entrada de glosario [Administración, Gestionar glosario, Usuario avanzado]
Eliminar entrada de glosario [Administración, Gestionar glosario, Usuario avanzado]
Cargar entradas de glosario [Administración, Gestionar glosario, Usuario avanzado]
- Automatización
Utilizar automatización [Administración, Usuario avanzado]
- Proyectos
Editar configuración del proyecto [Administración]
Gestionar acceso al proyecto [Administración]
- Informes
Download reports [Administration]
- Capturas de pantalla
Add screenshot [Administration, Manage screenshots]
Edit screenshot [Administration, Manage screenshots]
Delete screenshot [Administration, Manage screenshots]
- Cadenas de origen
Edit source string info [Administration, Edit source]
- Cadenas
Añadir cadenas nuevas [Administración]
Ignore failing checks [Administration, Edit source, Power user, Review strings, Translate]
Edit strings [Administration, Edit source, Power user, Review strings, Translate]
Review strings [Administration, Review strings]
Editar cadena cuando son obligatorias las sugerencias [Administración, Revisar cadenas]
Edit source strings [Administration, Edit source, Power user]
- Sugerencias
Accept suggestions [Administration, Edit source, Power user, Review strings, Translate]
Add suggestions [Add suggestion, Administration, Edit source, Power user, Review strings, Translate]
Eliminar sugerencias [Administración]
Vote on suggestions [Administration, Edit source, Power user, Review strings, Translate]
- Traducciones
Start new translation [Administration, Manage languages, Power user]
Perform automatic translation [Administration, Manage languages]
Delete existing translations [Administration, Manage languages]
Start translation into a new language [Administration, Manage languages]
- Cargas
Definir autor/a de la traducción cargada [Administración]
Overwrite existing strings with an upload [Administration, Edit source, Power user, Review strings, Translate]
Upload translation strings [Administration, Edit source, Power user, Review strings, Translate]
- Sistema de control de versiones
Access the internal repository [Access repository, Administration, Manage repository, Power user]
Commit changes to the internal repository [Administration, Manage repository]
Push change from the internal repository [Administration, Manage repository]
Reset changes in the internal repository [Administration, Manage repository]
View upstream repository location [Access repository, Administration, Manage repository, Power user]
Actualizar el repositorio interno [Administración, Gestionar repositorio]
- Privilegios en todo el sitio
Utilizar interfaz de gestión
Añadir definiciones de idioma
Gestionar definiciones de idioma
Añadir grupos
Gestionar grupos
Añadir usuarios
Administrar usuarios
Gestionar anuncios
Gestionar memoria de traducción
Nota
The site wide privileges are not granted to any default role. These are powerful and quite close to the superuser status—most of them affect all the projects of your Weblate installation.
List of groups¶
The following groups are created upon installation (or after executing
setupgroups):
- Guests
Defines permissions for non authenticated users.
This group contains only anonymous users (see
ANONYMOUS_USER_NAME).You can remove roles from this group to limit permissions for non authenticated users.
Default roles: Add suggestion, Access repository
- Viewers
This role ensures visibility of public projects for all users. By default all users are members of this group.
By default all users are members of this group, using Asignaciones de grupo automático.
Default roles: none
- Users
Default group for all users.
By default all users are members of this group using Asignaciones de grupo automático.
Default roles: Power user
- Reviewers
Group for reviewers (see Flujos de trabajo de traducción).
Default roles: Review strings
- Managers
Group for administrators.
Default roles: Administration
Advertencia
Never remove the predefined Weblate groups and users, as this can lead to unexpected problems. If you do not want to use these features, just remove all privileges from them.