2. Weblate
3. Documentation
4. Italian
5. Browse

1 / 291

/ 291

Not translated strings

• Not translated strings • state:empty
• Strings needing action • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with labels • has:label
• Strings with context • has:context
• Strings needing action without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Translated string
• Age of string
• Number of words
• Number of comments
• Number of failing checks
• Key

Context	English	Italian	State
	If you are not administrating the whole Weblate installation and just have access to manage certain projects (like on `Hosted Weblate <https://hosted.weblate.org/>`_), your access control management options are limited to following settings. If you don’t need any complex setup, those are sufficient for you.
	You can limit user’s access to individual projects by selecting a different :guilabel:`Access control` setting. Available options are:
	:ref:`User management <manage-acl>` features will be disabled; by default all users are forbidden to performed any actions on the project. You will have to set up all the permissions using :ref:`custom-acl`.
	:guilabel:`Access control` can be changed in the :guilabel:`Access` tab of the configuration (:guilabel:`Manage` ↓ :guilabel:`Settings`) of each respective project.
	The default value can be changed by :setting:`DEFAULT_ACCESS_CONTROL`.
	Even for `Private` projects, some info about your project will be exposed: statistics and language summary for the whole instance will include counts for all projects despite the access control setting. Your project name and other information can’t be revealed through this.
	The actual set of permissions available for users by default in `Public`, `Protected`, and `Private` projects can be redefined by Weblate instance administrator using :ref:`custom settings <custom-acl>`.
	By turning on `Custom` access control, Weblate will remove all :ref:`special groups <manage-acl>` it has created for a selected project. If you are doing this without admin permission for the whole Weblate instance, you will instantly lose your access to manage the project.
	Users with the :guilabel:`Manage project access` privilege (see :ref:`privileges`) can manage users in projects with non-`Custom` access control. They can assign users to one of the following groups.
	For `Public`, `Protected` and `Private` projects:
	Review (only if :ref:`review workflow <reviews>` is turned on)
	Can approve translations during review.
	For `Protected` and `Private` projects only:
	Can translate the project and upload translations made offline.
	Can edit source strings (if allowed in the :ref:`project settings <component-manage_units>`) and source string info.
	Can manage VCS and access the exported repository.
	Can access billing info and settings (see :ref:`billing`).
	Unfortunately, it’s not possible to change this predefined set of groups for now. Also this way it’s not possible to give just some additional permissions to all users.
	For non-`Custom` access control an instance of each group described above is actually defined for each project. The actual name of those groups will be ``Project@Group``, also displayed in the Django admin interface this way. Although they can’t be edited from Weblate user-interface.
	These features are available on the :guilabel:`Access control` page, which can be accessed from the project’s menu :guilabel:`Manage` ↓ :guilabel:`Users`.