diff --git a/.github/styles/config/vocabularies/Decidim/accept.txt b/.github/styles/config/vocabularies/Decidim/accept.txt index 81496daa51..d1e37358a3 100644 --- a/.github/styles/config/vocabularies/Decidim/accept.txt +++ b/.github/styles/config/vocabularies/Decidim/accept.txt @@ -1,2 +1,10 @@ Decidim -moderations \ No newline at end of file +CSV +Config +[Nn]ickame +[Ee]mail +[Oo]fficialize +[Oo]fficialization +[Oo]fficializing +Reoffficialize +moderations diff --git a/docs/en/modules/admin/assets/images/admin_user_group_verification.png b/docs/en/modules/admin/assets/images/admin_user_group_verification.png deleted file mode 100644 index 8a2a747244..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_user_group_verification.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admin_user_group_verification_actions.png b/docs/en/modules/admin/assets/images/admin_user_group_verification_actions.png deleted file mode 100644 index 5e0edf4183..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_user_group_verification_actions.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admin_user_group_verification_csv.png b/docs/en/modules/admin/assets/images/admin_user_group_verification_csv.png deleted file mode 100644 index 325dcaa530..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_user_group_verification_csv.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admins.png b/docs/en/modules/admin/assets/images/admins.png deleted file mode 100644 index 5f2fe6b73c..0000000000 Binary files a/docs/en/modules/admin/assets/images/admins.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admins_invite.png b/docs/en/modules/admin/assets/images/admins_invite.png deleted file mode 100644 index 9798d05f86..0000000000 Binary files a/docs/en/modules/admin/assets/images/admins_invite.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_account.png b/docs/en/modules/admin/assets/images/authorizations_account.png deleted file mode 100644 index 7b820221f3..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_account.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_admin_default.png b/docs/en/modules/admin/assets/images/authorizations_admin_default.png deleted file mode 100644 index 68e7438ea3..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_admin_default.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_admin_revocation.png b/docs/en/modules/admin/assets/images/authorizations_admin_revocation.png deleted file mode 100644 index 88c4484bf2..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_admin_revocation.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_confirm.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_confirm.png deleted file mode 100644 index c7cb0c1037..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_confirm.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_edit.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_edit.png deleted file mode 100644 index b4830af00a..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_edit.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_ongoing.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_ongoing.png deleted file mode 100644 index 824fa347d9..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_ongoing.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_request.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_request.png deleted file mode 100644 index 2ff188dbe3..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_request.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verified.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verified.png deleted file mode 100644 index 65996b8a2a..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verified.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verify.png b/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verify.png deleted file mode 100644 index 211b2bd357..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_code_postal_letter_verify.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_account_choose.png b/docs/en/modules/admin/assets/images/authorizations_id_document_account_choose.png deleted file mode 100644 index abb5b8b81f..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_account_choose.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_configuration.png b/docs/en/modules/admin/assets/images/authorizations_id_document_configuration.png deleted file mode 100644 index 85b625b706..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_configuration.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_configuration_offline.png b/docs/en/modules/admin/assets/images/authorizations_id_document_configuration_offline.png deleted file mode 100644 index 8baab477a7..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_configuration_offline.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_button.png b/docs/en/modules/admin/assets/images/authorizations_id_document_offline_button.png deleted file mode 100644 index 7a0f46b531..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_button.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_confirm.png b/docs/en/modules/admin/assets/images/authorizations_id_document_offline_confirm.png deleted file mode 100644 index 85dec306b8..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_confirm.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_request.png b/docs/en/modules/admin/assets/images/authorizations_id_document_offline_request.png deleted file mode 100644 index 294c93d328..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_offline_request.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_online.png b/docs/en/modules/admin/assets/images/authorizations_id_document_online.png deleted file mode 100644 index 3a90faad4b..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_online.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_online_confirm.png b/docs/en/modules/admin/assets/images/authorizations_id_document_online_confirm.png deleted file mode 100644 index f57b4faa68..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_online_confirm.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_online_pending.png b/docs/en/modules/admin/assets/images/authorizations_id_document_online_pending.png deleted file mode 100644 index 5a90b0df43..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_online_pending.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_id_document_online_rejected.png b/docs/en/modules/admin/assets/images/authorizations_id_document_online_rejected.png deleted file mode 100644 index 246928f934..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_id_document_online_rejected.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_organization_census.png b/docs/en/modules/admin/assets/images/authorizations_organization_census.png deleted file mode 100644 index 90a2f965a2..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_organization_census.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_organization_census_account.png b/docs/en/modules/admin/assets/images/authorizations_organization_census_account.png deleted file mode 100644 index f0d1f799bb..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_organization_census_account.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_organization_census_imported.png b/docs/en/modules/admin/assets/images/authorizations_organization_census_imported.png deleted file mode 100644 index 54af36e6aa..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_organization_census_imported.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/authorizations_organization_census_verified.png b/docs/en/modules/admin/assets/images/authorizations_organization_census_verified.png deleted file mode 100644 index 41012ffd2f..0000000000 Binary files a/docs/en/modules/admin/assets/images/authorizations_organization_census_verified.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/icons/action_clock.png b/docs/en/modules/admin/assets/images/icons/action_clock.png new file mode 100644 index 0000000000..e49103b6f7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_clock.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_contact.png b/docs/en/modules/admin/assets/images/icons/action_contact.png new file mode 100644 index 0000000000..cb2061a885 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_contact.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_delete.png b/docs/en/modules/admin/assets/images/icons/action_delete.png new file mode 100644 index 0000000000..4755d155d7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_delete.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_impersonate.png b/docs/en/modules/admin/assets/images/icons/action_impersonate.png new file mode 100644 index 0000000000..53bef80a0e Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_impersonate.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_promote.png b/docs/en/modules/admin/assets/images/icons/action_promote.png new file mode 100644 index 0000000000..76ae3f50bf Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_promote.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_reofficialize.png b/docs/en/modules/admin/assets/images/icons/action_reofficialize.png new file mode 100644 index 0000000000..5ee35af16c Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_reofficialize.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_resend.png b/docs/en/modules/admin/assets/images/icons/action_resend.png new file mode 100644 index 0000000000..6e095cd254 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_resend.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_show_email.png b/docs/en/modules/admin/assets/images/icons/action_show_email.png new file mode 100644 index 0000000000..fed86c47bb Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_show_email.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_transfer_user.png b/docs/en/modules/admin/assets/images/icons/action_transfer_user.png new file mode 100644 index 0000000000..1fdcc1ba86 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_transfer_user.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_verify.png b/docs/en/modules/admin/assets/images/icons/action_verify.png new file mode 100644 index 0000000000..727bfd2057 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_verify.png differ diff --git a/docs/en/modules/admin/assets/images/participants/admin_user_group_verification.png b/docs/en/modules/admin/assets/images/participants/admin_user_group_verification.png new file mode 100644 index 0000000000..3295b2c613 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/admin_user_group_verification.png differ diff --git a/docs/en/modules/admin/assets/images/participants/admin_user_group_verification_csv.png b/docs/en/modules/admin/assets/images/participants/admin_user_group_verification_csv.png new file mode 100644 index 0000000000..4832459777 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/admin_user_group_verification_csv.png differ diff --git a/docs/en/modules/admin/assets/images/participants/admins.png b/docs/en/modules/admin/assets/images/participants/admins.png new file mode 100644 index 0000000000..ce4c85e94a Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/admins.png differ diff --git a/docs/en/modules/admin/assets/images/participants/admins_invite.png b/docs/en/modules/admin/assets/images/participants/admins_invite.png new file mode 100644 index 0000000000..008fe8c07e Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/admins_invite.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_admin_default.png b/docs/en/modules/admin/assets/images/participants/authorizations_admin_default.png new file mode 100644 index 0000000000..06bb6d4a02 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_admin_default.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_admin_revocation.png b/docs/en/modules/admin/assets/images/participants/authorizations_admin_revocation.png new file mode 100644 index 0000000000..f3806c5fee Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_admin_revocation.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_confirm.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_confirm.png new file mode 100644 index 0000000000..c328a4ae27 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_confirm.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_edit.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_edit.png new file mode 100644 index 0000000000..f0cbddba8d Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_edit.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_ongoing.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_ongoing.png new file mode 100644 index 0000000000..7e22e8b729 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_ongoing.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_request.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_request.png new file mode 100644 index 0000000000..6715f4fc5b Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_request.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verified.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verified.png new file mode 100644 index 0000000000..5246bfe983 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verified.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verify.png b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verify.png new file mode 100644 index 0000000000..8c048f5648 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_code_postal_letter_verify.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_account_choose.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_account_choose.png new file mode 100644 index 0000000000..69ea7de765 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_account_choose.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration.png new file mode 100644 index 0000000000..b42950aa27 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration_offline.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration_offline.png new file mode 100644 index 0000000000..a8dad3b160 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_configuration_offline.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_button.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_button.png new file mode 100644 index 0000000000..ae1ad6c6aa Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_button.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_confirm.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_confirm.png new file mode 100644 index 0000000000..83bb8a1b18 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_confirm.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_request.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_request.png new file mode 100644 index 0000000000..719f8c2604 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_offline_request.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online.png new file mode 100644 index 0000000000..1ffdcd186c Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_confirm.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_confirm.png new file mode 100644 index 0000000000..7ab054e84a Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_confirm.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_pending.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_pending.png new file mode 100644 index 0000000000..cef2d98178 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_pending.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_rejected.png b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_rejected.png new file mode 100644 index 0000000000..175964c3bb Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_id_document_online_rejected.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_organization_census.png b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census.png new file mode 100644 index 0000000000..b8d735f194 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_account.png b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_account.png new file mode 100644 index 0000000000..17e4c47cf9 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_account.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_imported.png b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_imported.png new file mode 100644 index 0000000000..81428e0962 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_imported.png differ diff --git a/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_verified.png b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_verified.png new file mode 100644 index 0000000000..629e4182e7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/authorizations_organization_census_verified.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_conversation.png b/docs/en/modules/admin/assets/images/participants/participants_conversation.png new file mode 100644 index 0000000000..d1423b458f Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_conversation.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_button.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_button.png new file mode 100644 index 0000000000..0ccf23949a Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_button.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_logs.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_logs.png new file mode 100644 index 0000000000..ea6757c8a0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_logs.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_no_auth.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_no_auth.png new file mode 100644 index 0000000000..4dfb6c78d7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_backend_list_no_auth.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_form.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_form.png new file mode 100644 index 0000000000..c8556358e7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_form.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_promotion.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_promotion.png new file mode 100644 index 0000000000..15c65f829f Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_promotion.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_impersonations_user.png b/docs/en/modules/admin/assets/images/participants/participants_impersonations_user.png new file mode 100644 index 0000000000..194d891ad3 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_impersonations_user.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_menu.png b/docs/en/modules/admin/assets/images/participants/participants_menu.png new file mode 100644 index 0000000000..9977dcc76c Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_menu.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_officialize.png b/docs/en/modules/admin/assets/images/participants/participants_officialize.png new file mode 100644 index 0000000000..077f728db1 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_officialize.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_participants.png b/docs/en/modules/admin/assets/images/participants/participants_participants.png new file mode 100644 index 0000000000..7714effcd5 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_participants.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_show_email.png b/docs/en/modules/admin/assets/images/participants/participants_show_email.png new file mode 100644 index 0000000000..c570b83873 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_show_email.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_showed_email.png b/docs/en/modules/admin/assets/images/participants/participants_showed_email.png new file mode 100644 index 0000000000..dd2986b56d Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_showed_email.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_showed_email_admin_log.png b/docs/en/modules/admin/assets/images/participants/participants_showed_email_admin_log.png new file mode 100644 index 0000000000..eeceb0f326 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_showed_email_admin_log.png differ diff --git a/docs/en/modules/admin/assets/images/participants/participants_sidebar_menu.png b/docs/en/modules/admin/assets/images/participants/participants_sidebar_menu.png new file mode 100644 index 0000000000..2682c36f49 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/participants_sidebar_menu.png differ diff --git a/docs/en/modules/admin/assets/images/participants/user_group_frontend_show.png b/docs/en/modules/admin/assets/images/participants/user_group_frontend_show.png new file mode 100644 index 0000000000..e24d0a30b7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/user_group_frontend_show.png differ diff --git a/docs/en/modules/admin/assets/images/participants/user_group_verified.png b/docs/en/modules/admin/assets/images/participants/user_group_verified.png new file mode 100644 index 0000000000..fd7e807870 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/user_group_verified.png differ diff --git a/docs/en/modules/admin/assets/images/participants/verifications_conflicts.png b/docs/en/modules/admin/assets/images/participants/verifications_conflicts.png new file mode 100644 index 0000000000..fb7b5ca311 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/verifications_conflicts.png differ diff --git a/docs/en/modules/admin/assets/images/participants/verifications_conflicts_transfer_user.png b/docs/en/modules/admin/assets/images/participants/verifications_conflicts_transfer_user.png new file mode 100644 index 0000000000..3fcb08a258 Binary files /dev/null and b/docs/en/modules/admin/assets/images/participants/verifications_conflicts_transfer_user.png differ diff --git a/docs/en/modules/admin/assets/images/participants_conversation.png b/docs/en/modules/admin/assets/images/participants_conversation.png deleted file mode 100644 index d8b8416223..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_conversation.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_impersonations.png b/docs/en/modules/admin/assets/images/participants_impersonations.png deleted file mode 100644 index 4794d1582d..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_impersonations.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_impersonations_form.png b/docs/en/modules/admin/assets/images/participants_impersonations_form.png deleted file mode 100644 index 642828e6a1..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_impersonations_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_impersonations_managed.png b/docs/en/modules/admin/assets/images/participants_impersonations_managed.png deleted file mode 100644 index 21872430e1..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_impersonations_managed.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_impersonations_promotion.png b/docs/en/modules/admin/assets/images/participants_impersonations_promotion.png deleted file mode 100644 index 47cf11ed00..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_impersonations_promotion.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_impersonations_user.png b/docs/en/modules/admin/assets/images/participants_impersonations_user.png deleted file mode 100644 index 8f21421698..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_impersonations_user.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_menu.png b/docs/en/modules/admin/assets/images/participants_menu.png deleted file mode 100644 index d1e879815d..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_menu.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_officialize.png b/docs/en/modules/admin/assets/images/participants_officialize.png deleted file mode 100644 index 681878e9a1..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_officialize.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_participants.png b/docs/en/modules/admin/assets/images/participants_participants.png deleted file mode 100644 index b97172273c..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_participants.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_participants_actions.png b/docs/en/modules/admin/assets/images/participants_participants_actions.png deleted file mode 100644 index 08809e31ee..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_participants_actions.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_participants_actions_officialize.png b/docs/en/modules/admin/assets/images/participants_participants_actions_officialize.png deleted file mode 100644 index bbc8ae1e95..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_participants_actions_officialize.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_show_email.png b/docs/en/modules/admin/assets/images/participants_show_email.png deleted file mode 100644 index eebf9dca61..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_show_email.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_showed_email.png b/docs/en/modules/admin/assets/images/participants_showed_email.png deleted file mode 100644 index ce7df477aa..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_showed_email.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_showed_email_admin_log.png b/docs/en/modules/admin/assets/images/participants_showed_email_admin_log.png deleted file mode 100644 index 6d72039858..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_showed_email_admin_log.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/participants_sidebar_menu.png b/docs/en/modules/admin/assets/images/participants_sidebar_menu.png deleted file mode 100644 index 591bcc0247..0000000000 Binary files a/docs/en/modules/admin/assets/images/participants_sidebar_menu.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/verifications_conflicts.png b/docs/en/modules/admin/assets/images/verifications_conflicts.png deleted file mode 100644 index b6de1a96ab..0000000000 Binary files a/docs/en/modules/admin/assets/images/verifications_conflicts.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/verifications_conflicts_transfer_user.png b/docs/en/modules/admin/assets/images/verifications_conflicts_transfer_user.png deleted file mode 100644 index faabf213f9..0000000000 Binary files a/docs/en/modules/admin/assets/images/verifications_conflicts_transfer_user.png and /dev/null differ diff --git a/docs/en/modules/admin/pages/participants.adoc b/docs/en/modules/admin/pages/participants.adoc index a7efde5673..9eec5591b2 100644 --- a/docs/en/modules/admin/pages/participants.adoc +++ b/docs/en/modules/admin/pages/participants.adoc @@ -1,21 +1,26 @@ = Participants -Sometimes as an administrator you'll need to make certain tasks with participants, among them: +== Understand the basics -* To give permissions to other administrators so they can manage platform's content -* To verify user groups (organizations or collectives) -* To verify participants -* To recognize that a participant has a special status in the platform, with Officializations -* To authenticate that a person has the right to vote, with Authorizations -* To contact a participant +The participants tab allow you to make certain tasks with participants, among them: -You can access this section on the main sidebar of the admin panel. +* To manage access rights to the platform administration +* To contact participants +* To manage participants access to specific spaces +* To certify the identity of specific participants +* To certify the authenticity of user organizations or collectives -image:participants_menu.png[Participants menu] +== Configuration -Once you're in you can see all the different kind of participants and actions that you can do: +To access the Participants configuration panel, go in the administration panel and click the "Participants" item in the administration navigation bar. -image:participants_sidebar_menu.png[Participants sidebar menu] +image::participants/participants_menu.png[Participants menu] + +There, you first see the list of administrators of the platform. + +image::participants/participants_sidebar_menu.png[Participants sidebar menu] + +In the secondary navigation panel, you can see all the participants configuration possibilities: * xref:admin:participants/admins.adoc[Admins] * xref:admin:participants/groups.adoc[Groups] @@ -26,4 +31,12 @@ image:participants_sidebar_menu.png[Participants sidebar menu] * xref:admin:participants/authorizations.adoc[Authorizations] ** xref:admin:participants/authorizations/identity_documents.adoc[Identity documents] ** xref:admin:participants/authorizations/code_postal_letter.adoc[Code by postal letter] -** xref:admin:participants/authorizations/census.adoc[Organization's census] \ No newline at end of file +** xref:admin:participants/authorizations/census.adoc[Organization's census] + +Some of those items might not appear in this menu, because they aren't enabled. +To check how to enable them, go on the missing item documentation article. + +== Examples + +You want to add your colleagues so they can edit the platform. +You want to set specific flows for participants to be able to participate in a specific participatory space. diff --git a/docs/en/modules/admin/pages/participants/admins.adoc b/docs/en/modules/admin/pages/participants/admins.adoc index 0746ef9183..89d30a1f8d 100644 --- a/docs/en/modules/admin/pages/participants/admins.adoc +++ b/docs/en/modules/admin/pages/participants/admins.adoc @@ -1,21 +1,74 @@ -= Admins += Administrators -In the administrator listing page you can see all the administrators of the platform: +Administrators are the persons managing the organization, creating the processes, managing the platform as a whole +They can be of two types: -image:admins.png[Admins list] +* Administrators: have access to all the platform configuration. +* Participant managers: can only manage participants xref:admin:participants/impersonations.adoc[impersonations]. -Here you can: +image:participants/admins.png[Admins list] -* invite new administrators -* revoke administrators permissions -* see when was the last time an administrator logged in +== Invite an administrator -For inviting a new administrator, you need to go to the button "New user" and fill -the form with the admin username, email and which role will they have: +To invite an administrator, click the "New admin" button at the top right of the page. +You can invite an already registered or a non registered participant. -* Admin: to give full access to the platform -* Participant manager: to give permission to only do xref:admin:participants/impersonations.adoc[Impersonations] +image:participants/admins_invite.png[Invite participant as administrator form] -image:admins_invite.png[Invite participant as administrator form] +.New administrator form -You can invite an already registered or a non registered participant. \ No newline at end of file +|=== +|Field |Type |Description + +|Name +|Required +|Name of the administrator. If they already have an account, it changes automatically for their username. + +|Email +|Required +|Email of the participant to invite. If they don't have an account related to this email, they should receive an invitation email to create an account. Otherwise, they won't be notified. + +|Role +|Required +|Administrator or Participant manager + +|=== + +If an administrator doesn't already have an account, but didn't register, you can also Resend the invitation. + +== Manage administrators + +You can find all the administrators on the administrators list in the administration panel, with: +* *Role*: type of administrator rights, can only be Administrator or Participant manager. +* *Name*: name of the participant. +* *Email*: email of the participant. +* *Invitation sent at*: date and time of the email invitation. +* *Invitation accepted at*: when they accepted the email invitation. +* *Last log in date*: date of the administrator last connection. +* *Creation date*: date of the participant account creation. + +You can filter and sort this list by clicking the "Filter" button and the columns headers. +You can also search for administrators by email, name, or nickname in the search bar. + +=== Actions + +|=== +|Icon |Name |Definition |Condition + +|image:icons/action_resend.png[Resend invitation icon] +|Resend invitation +|To resend an invitation email to the participant. +|Available when the participant didn't accept the invitation. + +|image:icons/action_delete.png[Delete icon] +|Delete +|To revoke the participant's administration access rights. +|Available for all administrators, except for the first one. + +|=== + +=== Revoke administrator permissions + +When an administrator doesn't need access anymore, you should revoke their rights by clicking the "Delete" button. +You need to confirm the rights deletion to completely remove their rights. +Revoking administrator permissions don't delete the participant account. \ No newline at end of file diff --git a/docs/en/modules/admin/pages/participants/authorizations.adoc b/docs/en/modules/admin/pages/participants/authorizations.adoc index 8c460ed37e..eab3f00d5c 100644 --- a/docs/en/modules/admin/pages/participants/authorizations.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations.adoc @@ -1,32 +1,20 @@ = Authorizations -This section allows you to manage participants' authorizations. It depends on which Authorizations you have configured and -enabled by your developers. To understand more what are authorizations and how to configure them, please refer to the -xref:customize:authorizations.adoc[Authorizations section in the Customize Guide]. - -With authorizations an administrator can define different permissions so participants can make some actions in a component. -For instance you can configure that only participants who have verified herselves by their identity documents can vote on -proposals in a participatory process. +Authorizations allow to give specific participation rights to participants who have completed a verification process. +This verification process can be direct, have multiple steps, be online or in-person. -A participant can see which authorizations do they have available in their account settings. +For instance you can configure that only participants who have verified themselves by their identity documents can vote on +proposals in a specific participatory process. -image:authorizations_account.png[Authorizations in participants account] - -== Authorizations revocation +NOTE: Several authorizations are available by default, but you can also develop your own authorizations. -A default Decidim installation will not have verified participants. +== Enable / disable authorizations -image:authorizations_admin_default.png[Authorizations in a default installation] - -In the moment that there are some participants verified, an administrator can revoke all the authorizations, as the attributes -that give permissions to those participants could be changed in time and the platform didn't receive these changes in the -participants statuses. For instance, an identity document of a participant could be expired, or if a participant have been -authorized by the "code by postal letter", that participant could move in the meantime. - -image:authorizations_admin_revocation.png[Authorizations revocation] +To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask the instance implementer. +To understand more what are authorizations and how to configure them, please refer to the +xref:customize:authorizations.adoc[Authorizations section in the Customize Guide]. -It's possible to revoke all the authorizations with "Revoke all", or to only revoke authorizations before a given date. -Another possiblity is to revoke only the xref:admin:participants/impersonations.adoc[impersonated participants]. +Participants can access, update, or delete their authorizations in their xref:admin:features/my_account/authorizations.adoc[account]. == Verification methods @@ -38,3 +26,19 @@ Some of the available authorizations by default are: If any of these authorizations are not useful for your needs, talk with your implementer to see other alternatives. Learn more about xref:customize:authorizations.adoc[Authorizations in the Customize Guide section]. + +== Authorizations revocation + +A default Decidim installation don't have verified participants. + +image::participants/authorizations_admin_default.png[Authorizations in a default installation] + +From the moment some participants get verified with an authorization, administrators can revoke all the authorizations at once. +Indeed, after some time, some of the verifications can be deprecated. +For instance, identity documents expire after some time, or participants can move from a city. +Then, an administrator can want to force participants to renew their verification information. + +image:participants/authorizations_admin_revocation.png[Authorizations revocation] + +It's possible to revoke all the authorizations with "Revoke all," or to only revoke authorizations created before a given date. +Another possibility is to revoke only the verifications for xref:admin:participants/impersonations.adoc[impersonated participants]. diff --git a/docs/en/modules/admin/pages/participants/authorizations/census.adoc b/docs/en/modules/admin/pages/participants/authorizations/census.adoc index bc81ab9578..cc2f27f868 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/census.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/census.adoc @@ -2,33 +2,33 @@ The process is as follows: -. Admins upload a CSV with the emails of the accepted participants -. Participants go to its accounts and requests to be verified +. Admins upload a CSV with the emails of the verified participants +. Participants go to their account and request to be verified . Only participants with an email in that CSV file can get verified -NOTE: is this too simple and you need more features related to CSV census imports? -Check all the CSV or file based authorizations in our https://decidim.org/modules/[Modules page]. +NOTE: This authorization is too basic and you need more features related to CSV census imports? +Check all the CSV or file based authorizations in the https://decidim.org/modules/[Modules page]. -== 1. An administrator uploads the CSV of the participants +== 1. CSV upload -In the admin panel, the administrator can review the request by going to the "Organization's census" in the "Participants" section. +In the administrator panel, you can upload a CSV file by clicking on "Organization's census" in the "Participants" section. -image:authorizations_organization_census.png[Organization's census in admin panel] +image::participants/authorizations_organization_census.png[Organization's census in administrator panel] -After the CSV is imported then the administrator can see how many participants where imported. They can also delete this +After the CSV is imported then the administrator can see how many participants were imported. They can also delete this imported census. -image:authorizations_organization_census_imported.png[Imported CSV] +image::participants/authorizations_organization_census_imported.png[Imported CSV] -== 2. A participant requests to be verified +== 2. Participant request By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, a participant can request to be verified. -image:authorizations_organization_census_account.png[Organization's census in participant's accounts] +image::participants/authorizations_organization_census_account.png[Organization's census in participant's accounts] -== 3. The participant is verified (or not) +== 3. Participant verification After is verified, as with other verifications, they can see it in their account settings. -image:authorizations_organization_census_verified.png[Verified by organization's census] \ No newline at end of file +image::participants/authorizations_organization_census_verified.png[Verified by organization's census] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc b/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc index 9abae9a45d..faacc51af5 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc @@ -1,57 +1,59 @@ = Code by postal letter authorization -This authorization allows a participant to request for a verification code to be sent to its address, to confirm that they -live or work in this place. They will need to then fill the code in the platform. +This authorization allows a participant to request for a verification code to be sent to an address, to confirm that they +live or work in this place. They then need to fill the received code in the platform. + +NOTE: If you don't want to use this authorization, you should turn it off in the xref:admin:system.adoc[system panel]. The process is: -. Participants request a verification code to be sent to their address. +. Participant request a verification code to be sent to an address. . An administrator sends the letter to their address with the verification code. . An administrator marks the letter as sent. -. Once you mark the letter as sent, the participant will be able to introduce the code. -. If this code matchs, then they get verified. +. Once you mark the letter as sent, the participant is able to introduce the code. +. If this code matches, then they get verified. -== 1. A participant request the verification code +== 1. Verification code request By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, -a participant can see the form for filling in their full address to request the verification code. +a participant can see the form requesting their full address. -image:authorizations_code_postal_letter_request.png[Code by postal letter request by participant] +image::participants/authorizations_code_postal_letter_request.png[Code by postal letter request by participant] -If they try to edit it, they will see this message: +If they try to edit it, they see this message: -image:authorizations_code_postal_letter_edit.png[Edit the postal letter request] +image::participants/authorizations_code_postal_letter_edit.png[Edit the postal letter request] This is because the letter could be in the process of being sent. If this needs to be corrected, then the participant needs -to contact to the organization. +to contact a platform administrator. -== 2. An administrator review this request and sent the letter +== 2. Administrator review -In the admin panel, the administrator can review the request by going to the "Code by postal letter" in the "Participants" section. +In the administration panel, the administrator can review the request by going to the "Code by postal letter" in the "Participants" section. -image:authorizations_code_postal_letter_ongoing.png[Code by postal letter ongoing panel in admin] +image::participants/authorizations_code_postal_letter_ongoing.png[Code by postal letter ongoing panel in administration] -Here they can see the verification code and can send it to the participant by mail. After the code is sent they can mark it -as sent with the icon image:action_mark_as_sent.png[Mark as sent]. It'll also show when the letter was sent. +Here they can see the verification code and can send it to the participant by postal letter. After the code is sent they can mark it +as such with the icon image:icons/action_verify.png[Mark as sent]. It'll also show when the letter was sent. -== 3. A participant fills in the verification code +== 3. Participant validate the code After the participant has received the code, they can go to their account settings and click in the "Code by postal letter" -verfication method. +verification method. -image:authorizations_code_postal_letter_verify.png[Code by postal letter ongoing in the participant account] +image::participants/authorizations_code_postal_letter_verify.png[Code by postal letter ongoing in the participant account] -Then they will see the form for confirming the code. +Then they can fill the form with the code they received. -image:authorizations_code_postal_letter_confirm.png[Code by postal letter confirmation form] +image::participants/authorizations_code_postal_letter_confirm.png[Code by postal letter confirmation form] -== 4. The verification code matches or not +== 4. Code match -If the verification code matches, then the participant will see the message "Congratulations. You've been successfully verified". +If the verification code matches, then the participant sees the message "Congratulations. You've been successfully verified." -On the other hand, if the verification code doesn't match, then the participant will see the message "Your verification -code doesn't match ours. Please double-check the letter we sent to you." +On the other hand, if the verification code doesn't match, then the participant see an error asking to double-check the code in +the letter. -After is verified, as with other verifications, they can see it in their account settings. +After a participant is verified, as with other verifications, they can see it in their account settings. -image:authorizations_code_postal_letter_verified.png[Verified by code by postal letter] +image::participants/authorizations_code_postal_letter_verified.png[Verified by code by postal letter] diff --git a/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc b/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc index bd959dd2c6..72df53914b 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc @@ -1,23 +1,23 @@ = Identity documents authorization -This authorization allows a participant to upload its identity documents. These documents depend on the organization, -they could be a driver's license, a passport, a national identity card, a club membership card, etc. +This authorization allows a participant to upload its identity documents into the platform, and get their account verified. +These documents depend on the organization, they could be a driver's license, a passport, a national identity card, +a club membership card, etc. -These documents will be reviewed by an administrator to accept or reject them. It's possible to do this process in two ways: Online or Offline. +NOTE: If you don't want to collect any data, you should turn it off in the xref:admin:system.adoc[system panel]. -* Online: the participant will be asked to upload the documents, and the administrator will review these documents. -* Offline: the participant will be asked to fill in some data, and then they will need to go to a presential place to show their documents face to face. +These documents are reviewed by an administrator who can accept or reject them. It's possible to do this process +in two ways: -== Configuration +* *Online*: the participant is asked to upload the documents, and the administrator reviews these documents. +* *Offline*: the participant is asked to fill in some data, and then they need to go to a physical place +to show their documents face to face. -By clicking on the btn:[Config] button in this section, an administrator can configure the settings for this authorization. +== Configuration -image:authorizations_id_document_configuration.png[ID document authorization configuration] +Click the "Config" button to configure the authorization. -NOTE: As you can see, this authorization is based in the original implementers reality, in this case in the Spanish identities document types. -For instance, we're giving as options for document types "DNI, NIE or Passport" or we're asking for "Document number (with letter)" -You can change this by xref:customize:code.adoc[code customizing or overriding] these things. We also accept xref:contribute:governance.adoc[Pull Request contributions] -so it's possible to configure this. +image::participants/authorizations_id_document_configuration.png[ID document authorization configuration] .ID Documents authorization configuration |=== @@ -35,47 +35,51 @@ for certain hours? |=== -== Online +== Online verification The process is: . Participants fill in their document type and number and upload a copy of their document. . An administrator fills in the information present in the uploaded image. . The information should match whatever the user filled in. -. If the administrator can't clearly see the information or they can't get it verified, they can reject the request and +. If the administrator can't see the information or they can't get it verified, they can reject the request and the user will be able to fix it. -=== 1. A participant fill in the document information and uploads a copy of their document +=== 1. Participant authorization creation By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, a participant can see the form for uploading a copy of their document. They also need to fill in their document type and number. -image:authorizations_id_document_online.png[ID document authorization online form] +image::participants/authorizations_id_document_online.png[ID document authorization online form] + +NOTE: You can change the document types options by xref:customize:code.adoc[customizing or overriding the code]. -=== 2. An administrator review this document +=== 2. Administrator document review -After this document is uploaded, an administrator can review it by going to the Identity documents section in the admin +After this document is uploaded, an administrator can review it by going to the Identity documents section in the administration panel. -image:authorizations_id_document_online_pending.png[ID document authorization pending online verification] +image::participants/authorizations_id_document_online_pending.png[ID document authorization pending online verification] -After clicking on the document, the administrator needs to see the image and fill in the document number. This needs to match -with the one provided by the participant. +After clicking on the verification id link or on the document, the administrator needs to review the image and fill in +the document number in the field. This number needs to match with the one provided by the participant. -image:authorizations_id_document_online_confirm.png[ID document authorization online confirmation form] +image:participants/authorizations_id_document_online_confirm.png[ID document authorization online confirmation form] -=== 3. The request is accepted or rejected +=== 3. Administrator decision -There are two actions an admin can do: +There are two actions an administrator can do: -* Accept: the participant will be fully authorized. -* Reject: the participant will be prompted to amend their documents +* Verify: the system checks if the document numbers entered by administrator and user are the same. +* Reject: the participant have to edit their authorization if they want to get verified. If the request is rejected then the participant can provide other pictures or document. -image:authorizations_id_document_online_rejected.png[ID document authorization rejected online verification] +image::participants/authorizations_id_document_online_rejected.png[ID document authorization rejected online verification] -== Offline +Once a participant is verified, their documents are deleted from the list. + +== Offline verification The process is: @@ -84,32 +88,32 @@ The process is: specific time to show their documents. . An administrator go to the "Offline verification" panel and fills in the information present in the physical documents. . The information should match whatever the user filled in. -. If the administrator can't clearly see the information or they can't get it verified, they can reject the request and -the user will be able to fix it. +. If the administrator can't see the information or they can't get it verified, they can reject the request and +the user is then able to fix it. -For this authorization to work, an administrator need to first configure it in the admin panel with the instructions explaining +For this authorization to work, an administrator need to first configure it in the administration panel with the instructions explaining what the participant need to do to finish the verification process. -image:authorizations_id_document_configuration_offline.png[ID document authorization configuration: offline instructions] +image:participants/authorizations_id_document_configuration_offline.png[ID document authorization configuration: offline instructions] -=== 1. A participant fill in the document information and follow the instructions +=== 1. Participant authorization creation By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, a participant can see the form for filling in their document type and number. -image:authorizations_id_document_offline_request.png[ID document authorization offline form] +image:participants/authorizations_id_document_offline_request.png[ID document authorization offline form] -=== 2. An administrator review this request +=== 2. Administrator document review -In the admin panel, the administrator can review the request by clicking in the "Offline verification" button. +In the administration panel, the administrator can review the request by clicking the "Offline verification" button. -image:authorizations_id_document_offline_button.png[ID document authorization offline button in admin] +image::participants/authorizations_id_document_offline_button.png[ID document authorization offline button in administration] -Then they will need to fill some data provided by the participant and by reviewing the document physically provided by them. +Then they need to fill some data provided by the participant and review the document physically provided. -image:authorizations_id_document_offline_confirm.png[ID document authorization offline confirmation form in admin] +image::participants/authorizations_id_document_offline_confirm.png[ID document authorization offline confirmation form in administration] -.ID Documents authorization offline flow +.ID Documents authorization offline form |=== |Field |Type |Description @@ -119,23 +123,23 @@ image:authorizations_id_document_offline_confirm.png[ID document authorization o |Type of the document |Required -|Can be: DNI, NIE or Passport +|Can be: ID or Passport -|Document number (with letter) +|Document number |Required |Document number of the participant. For instance, "12345678Z" |=== -=== 3. The request is accepted or rejected +=== 3. Administrator decision In the cases where the verifications don't match (meaning that the email or the document number provided by the -participant and the ones filled by the administrators aren't the same), then the participant needs to amend it with their +participant and the ones filled by the administrators aren't the same), then the participant needs to edit it within their user account. == Both -It's also possible to enable both of these verifications methods. In this case, the participant will be asked to choose +It's also possible to enable both of these verifications methods. In this case, the participant has to choose which kind of verification they want to do. -image:authorizations_id_document_account_choose.png[Choose ID document verification kind] +image::participants/authorizations_id_document_account_choose.png[Choose ID document verification kind] diff --git a/docs/en/modules/admin/pages/participants/groups.adoc b/docs/en/modules/admin/pages/participants/groups.adoc index e0f57dcb75..360668a962 100644 --- a/docs/en/modules/admin/pages/participants/groups.adoc +++ b/docs/en/modules/admin/pages/participants/groups.adoc @@ -1,117 +1,72 @@ -= User Groups += User groups -An user group is a group of participants. Depending in the installation and the context of the organization it could be disabled. This is enabled or disabled in the administration dashboard, in Settings -> Configuration -> Edit organization -> Enable groups. +User groups are entities created by participants to represent a structure, a club, an association, etc. +User groups can be managed by different administrators, and have several members. +If an administrator verifies a user group, then all the user group administrators can participate in the name of the group. -== Creation +image::participants/user_group_frontend_show.png[Frontend: show a user group] -This action is done by **a participant**. They need to go to their profile and in the sidebar there's a button that says "Create group": +== Enable / disable user groups -image:user_sidebar.png[User sidebar] +Administrators can enable or disable user groups in the xref:admin:configuration.adoc[Configuration] panel. -When clicked it'll open the "New group form": +When enabled, participants are able to create and manage groups from their profile. +To learn more about how participants can do this, go to the xref:admin:features/my_public_profile.adoc[public profile] article. -image:user_group_new_form.png[New user group form] +== Manage user groups -.New group form -|=== -|Field |Type |Description - -|Name -|Required -|Name of your organization, association, collective, group, etc. - -|Nickname -|Required -|Nickname of your organization, association, collective, group, etc. Do not use spaces nor accents. 20 characters maximum. +When a participant creates a user group, it adds a line in the user groups list in the administration panel, with: +* *Name*: name of the user group. +* *Nickame*: nickame of the user group. +* *Document number*: can be the identification number of the structure, like a company or association identification number. +* *Phone*: phone number of the structure or the administrator of the user group. +* *Participants count*: number of members of the user group. +* *Created at*: date of the user group creation. +* *State*: state of the verification, can only be pending, verified, or rejected. -|Email -|Required -|Email of your organization, association, collective, group, etc. +You can filter and sort this list by clicking the "Filter" button and the columns headers. +You can also search for user groups by email, name, or nickname in the search bar. -|Avatar -|Optional -|Guidance for image: Preferably a landscape image that does not have any text. The service crops the image. Maximum file size: 5MB. Allowed file extensions: jpg jpeg gif png bmp ico +image::participants/admin_user_group_verification.png[Admin panel: user group verifications] -|About -|Optional -|Description of what's this group. +A user group can have three states: -|Document number -|Optional -|Used for verifications. Do not use dashes nor spaces. +* Pending: waiting for an answer from an administrator +* Verified: an administrator verified the authenticity of this group +* Rejected: an administrator decided this group was not authentic or compliant -|Phone -|Optional -|Used for verifications. Do not use dashes nor spaces. +=== Actions |=== +|Icon |Name |Definition |Condition +|image:icons/action_verify.png[Verify icon] +|Verify +|To validate the verification of the user group. +|Available when the user group state is pending or rejected. -== Membership - -After a group has been created, it's possible to invite participants to become members of the group. After a participant has accepted to be part of this group then they can become an admin. - -The actions that can be done by a participant in the user group are: - -* Edit group profile -* Manage members -* Manage admins -* Invite participant -* Leave group - -image:user_group_invite_participant.png[User groups: invite a participant] - -== Group verifications - -image:admin_user_group_verification.png[Admin panel: user group verifications] - -This action is done by **an administrator**. A group can be: -* Pending -* Verified -* Rejected - -This can be done with the buttons at the sidebar: - -image:admin_user_group_verification_actions.png[Admin panel: user group verifications actions] +|image:icons/action_delete.png[Reject icon] +|Reject +|To reject the verification request of the user group. +|Available when the user group state is pending or verified. -When a user group is pending it can be verified or rejected. Once is verified it can be rejected and once is rejected it can be verified. - -If you want to verify multiple user groups at the same time you can do so with the option "Verify via CSV": - -image:admin_user_group_verification_csv.png[Admin panel: user group verifications CSV] - -.... -Upload your CSV file. It must have the official emails of the groups in your organization in the first column of the file, without headers. Only groups that have confirmed their email and that have an email appearing in the CSV file will be validated. -.... - -After a group is verified this is publicly visible in their nickname in the platform and there's a message in its profile: "This group is publicly verified, its name has been verified to correspond with its real name". - -image:user_group_verified.png[User group: verified icon] - -== Actions - -As a verified user group, there's some options that your participant account can do in behalf of the group, such as: - -=== Create a Debate, Proposal or Meeting - -There's a dropdown in the form during the creation process: - -image:user_group_create_debate.png[User group: create a debate] - -=== Make a comment +|=== -There's a dropdown in the form when making a comment: +=== Verify a group -image:user_group_make_comment.png[User group: make a comment] +To verify a group, an administrator should verify that the group exists and is legitimate to have an entity on the platform. +Administrator can call the group administrator on the phone number provided, or verify that the document number exists. -=== Endorse +After a group is verified, this is publicly visible in their nickname in the platform and there's a message in its profile: +"This group is publicly verified, its name has been verified to correspond with its real name." -When making an Endorse there's a modal window asking who do you want to make the endorse with: +image::participants/user_group_verified.png[User group: verified icon] -image:user_group_endorse.png[User group: endorse] +=== Verify by CSV -=== Conversations +If you want to verify multiple user groups at once, you can do so with the "Verify via CSV" button. -You can also have Conversations as a group. This is in the group profile page: +image::participants/admin_user_group_verification_csv.png[Admin panel: user group verifications CSV] -image:user_group_conversation.png[User group: conversations] +There, you can upload a CSV file, with a unique column without headers, containing the user groups emails you want to verify. +Only the groups that have confirmed their email and that have an email appearing in the CSV file will be verified. diff --git a/docs/en/modules/admin/pages/participants/impersonations.adoc b/docs/en/modules/admin/pages/participants/impersonations.adoc index 90912de6f8..098d8d2ad2 100644 --- a/docs/en/modules/admin/pages/participants/impersonations.adoc +++ b/docs/en/modules/admin/pages/participants/impersonations.adoc @@ -1,42 +1,76 @@ -= Participants Impersonations += Participants impersonations -For participants that don't have the knowledge or don't have an email for registering -an account, there's the Impersonation feature. +Sometimes, people don't have the time to create an account, or don't have the knowledge or ability to use technological tools. +Impersonations allow administrators and participant managers to enable those persons to participate anyway. -This allows an 'Administrator' or 'Participant manager' to search through a -Verification system for an already existing participant and also to create a -participant without email. +NOTE: In the code and the User Interface, *Impersonation* and *Managed Participants* are the same thing. -NOTE: At the code and the User Interface we say both *Impersonation* and *Managed -Participants*. It's the same thing. +== Enable / disable impersonations -## Panel +Impersonations are only available when at least one authorization is enabled for the organization. +Indeed, they allow the system to search through a Verification system for an already existing participant, and to create +a participant without the need for an email address. -image::participants_impersonations.png[Admin's Impersonations panel] +To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask your instance implementer. -This is the panel where you can find all the participants: +image::participants/participants_impersonations_backend_list_no_auth.png[Administrators Impersonations panel with no authorizations] -* by filtering by managed or not managed participants -* by searching by name +The different authorizations give you different possibilities: -After you've clicked in `Manage new participant` you'll go to the form to enter -the personal data to check against the verification: +* View impersonation logs only: When Identity documents, Code by postal letter, and/or Organization's census are enabled +* Impersonate existing and new users: Direct verification enabled, like example authorization or other custom direct authorizations. -image::participants_impersonations_form.png[Admin's Impersonations form] +NOTE: You can learn more regarding how to program your form authorization in +https://github.com/decidim/decidim/blob/develop/decidim-verifications/README.md[Decidim-verification README]. -NOTE: If you don't see the `Manage new participant` button, is because this feature -only works when you have a Verification of kind `direct` (also known -as `form authorizations`). See in your xref:admin:system.adoc[system panel] which -`Available authorizations` are enabled. You can learn more regarding how to program -your form authorization in https://github.com/decidim/decidim/blob/develop/decidim-verifications/README.md[decidim-verification README]. +image::participants/participants_impersonations_backend_list_logs.png[Administrators Impersonations panel with view log] -After this data is confirmed then there'll be a session for the participant for -30 minutes: +image::participants/participants_impersonations_backend_list_button.png[Administrators Impersonations panel with impersonation action] -image::participants_impersonations_user.png[Impersonated user session] +== Manage impersonations -Finally, it's also possible to Promote a participant, meaning that after a -participant has been managed, an administrator can add the email and send them -an Invitation: +You can find all the participants of the platform, with: +* *Name*: name of the participant. +* *Status*: if the participant is impersonated/managed or not. -image::participants_impersonations_promotion.png[Admin's promotion Impersonations] +You can filter this list by clicking the "Filter" button and search for participants by their name. + +=== Actions + +|=== +|Icon |Name |Definition |Condition + +|image:icons/action_impersonate.png[Impersonate icon] +|Impersonate +|To impersonate the participant. +|Available all the time. + +|image:icons/action_clock.png[View logs icon] +|View logs +|To view the impersonation history of the participant. +|Available all the time. + +|image:icons/action_promote.png[Promote icon] +|Promote +|To view the impersonation history of the participant. +|Available only for managed users. + +|=== + +=== Impersonate a participant + +Click the "Manage new participant" button. You are then able to enter the personal data to check against the verification: + +image::participants/participants_impersonations_form.png[Administrators Impersonations form] + +After this data is checked by the system, it opens a session for the participant for 30 minutes. +A banner at the top of the page reminds the administrator that they are impersonating the participant, and the remaining time. + +image::participants/participants_impersonations_user.png[Impersonated user session] + +=== Promote a managed participant + +Administrators can promote managed participants, to invite them to the create an account on the platform. +Click the "Promote" icon to be able to add an email address to the participant and invite them by email. + +image::participants/participants_impersonations_promotion.png[Administrators promotion Impersonations] diff --git a/docs/en/modules/admin/pages/participants/participants.adoc b/docs/en/modules/admin/pages/participants/participants.adoc index 8b82a34d4b..6b39fb2494 100644 --- a/docs/en/modules/admin/pages/participants/participants.adoc +++ b/docs/en/modules/admin/pages/participants/participants.adoc @@ -1,92 +1,90 @@ = Participants +Participants are all people with an account on the platform, whether they have confirmed their email address or not. In this page an administrator can: * Block a participant, for instance because they are spamming or acting against the Terms of Service -* Contact a participant with Decidim private messages (Conversations) +* Contact a participant with Decidim private messages * Officialize a participant -* See its email +* Show a participant email -image:participants_participants.png[Participants list] +image:participants/participants_participants.png[Participants list] -== Actions +== Manage participants -image:participants_participants_actions.png[Participants actions] +You can find all the participants here, with: +* *Name*: name of the participant, with a link to their profile. +* *Nickname*: nickname of the participant, with a link to their profile. +* *Created at*: date of the participant account creation. +* *Status*: if the participant is officialized or not. +* *Badge*: the officialization badge, given when officializing the participant. +* *Reports*: number of reports by different users. + +You can filter and sort this list by clicking the "Filter" button and the columns headers. +You can also search for participants by email, name, or nickname in the search bar. + +=== Actions |=== -|Icon |Name |Definition +|Icon |Name |Definition |Condition -|image:action_block.png[Block user] -|xref:_block_user[Block user] -|To block or moderate a participant. +|image:icons/action_block.png[Block user] +|Block / Unblock user +|To block or unblock a participant. See xref:admin:moderations/reported_users.adoc[Reported users] for more information. +|Block action is available for unblocked users, and vice versa. -|image:action_show_email.png[Show email] +|image:icons/action_show_email.png[Show email] |xref:_show_email_address[Show email address] -|To show an email of a participant. +|To show the email address of a participant. +|Available all the time. -|image:action_contact.png[Contact] +|image:icons/action_contact.png[Contact] |xref:_contact[Contact] -|To contact a participant with Decidim private messages (Conversations) +|To contact a participant through a private message. +|Available all the time. -|image:action_officialize.png[Officialize] +|image:icons/action_verify.png[Officialize] |xref:_officialize[Officialize] -|To recognize that a participant has a special status in the platform +|To recognize that a participant has a special status, like mayor, association's president, etc. +|Available for unofficialized participants. -|image:action_reofficialize.png[Reoffficialize] -|Reoffficialize -|To change an officialization. See xref:_officialize[Officialize] +|image:icons/action_reofficialize.png[Reoffficialize] +|Reofficialize +|To change the officialization badge. +|Available for officialized participants. -|image:action_unofficialize.png[Unofficialize] +|image:icons/action_delete.png[Unofficialize] |Unofficialize -|To revoke an officialization. See xref:_officialize[Officialize] -|=== - -=== Block user - -After clicking in this option you'll need to provide a justification why you're -blocking this participant: - -image:participants_block_user_justification.png[Justificate the blocked user action] - -Once a blocked participant tries to log-in they will see an error message: +|To revoke an officialization. +|Available for officialized participants. -image:participants_block_user_alert.png[Message shown to blocked user] +|=== -After a participant was blocked its name is changed to "Blocked user". +=== Show email address -See more at xref:admin:participants/reported_users.adoc[Reported users] +Sometimes, administrators need to find a user email address. They can click the "Show email address" option. +A modal appears, with the name of the participant, and an hidden field. -=== Show email address +image:participants/participants_show_email.png[Modal in show email] -After clicking this option, the admin will see a modal. They will have to click in -button "Show email address". +To show the email address, you need to click the "Show" button. -image:participants_show_email.png[Modal in show email] -image:participants_showed_email.png[Modal after the email is shown] +image:participants/participants_showed_email.png[Modal after the email is shown] -This action will be logged in the Admin actvity log. +For administration transparency, this action is logged in the activity logs. -image:participants_showed_email_admin_log.png[Admin activity log for show email] +image:participants/participants_showed_email_admin_log.png[Admin activity log for show email] === Contact -By clicking on this option, it will open the private messaging (Conversation) for -this participant. +To contact participants directly through the private messaging of the platform, click the "Contact" icon. -image:participants_conversation.png[Conversation with a participant]. +image:participants/participants_conversation.png[Conversation with a participant]. === Officialize -This option is useful to recognize that a participant has a special status in the -platform. For instance, if someone is the City Mayor, a City Councillor or the -President of an Association in an organization context. - -After Officializing a participant you can: - -- Change the Officialization text with "Reofficialize" -- Revoke the Officialization status with "Unofficialize" - -image:participants_officialize.png[Officialize a participant] -image:participants_participants_actions_officialize.png[Officialize a participant] - +This option is useful to recognize that a participant has a specific status in the +platform. For instance, if someone is the city mayor, a city councillor, the +president of an association, etc. +image:participants/participants_officialize.png[Officialize a participant] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc b/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc index 972d70114a..e11907e2dd 100644 --- a/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc +++ b/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc @@ -1,25 +1,52 @@ -= Verification's conflicts += Verifications conflicts -There are cases depending on which kind of verifications you've enabled that there could be verification's conflicts. +A verification conflict can happen when authorizations are enabled, and some participants create several accounts +or get impersonated. For instance: -. A participant get xref:admin:participants/impersonations.adoc[impersonated], and they don't provide an email -. Then they create an account and try to verify themselves with the Census verification +. A participant create an account, and get verified against an authorization. +. Then they create another account and try to get verified again against the same authorization. -For security, we try to be extra cautious in these cases, and we want that an administrator reviews these verifications. -As you can see, this depends a lot on which kind of verifications you've enabled in your organization, so it's easy to say -that most of the time an organization will not see any conflicts in this panel. +This can also happens with impersonations: -image:verifications_conflicts.png[Verification's conflicts panel] +. A participant get xref:admin:participants/impersonations.adoc[impersonated] with their data, but don't enter an email +. Then they create an account, and try to verify themselves with the same verification -== Transfer user +For security, try to be extra cautious in these cases, and make sure an administrator reviews these potential conflicts. +It depends a lot on which kind of verifications you've enabled in your organization, so most of the time an organization +don't see any conflicts appear in this panel. -An administrator can review these conflicts by clicking in the Transfer user image:action_transfer_user.png[Transfer user] icon. +image:participants/verifications_conflicts.png[Verification's conflicts panel] -Then they will see the Transfer user form, where they can provide a reason for the transfer. +When there is a verification conflict, administrators receive an email notification. -image:verifications_conflicts_transfer_user.png[] +== Manage verifications conflicts + +In the verifications conflict panel, you can find all the conflicts, with: +* *User*: name of the non managed participant who tried to get verified from their account. +* *Managed user*: name of the impersonated user with the same verification data. +* *Attempts*: number of time the user tried to get verified with their data. +* *Solved*: if the verification conflict was solved or not. + +You can search for conflicts by participant email, name, or nickname in the search bar. + +=== Actions + +|=== +|Icon |Name |Definition + +|image:icons/action_transfer_user.png[Transfer user] +|Transfer user +|To solve the verification conflict. + +|=== + +=== Transfer user + +The transfer user button allows to solve the conflict between both account. + +image:participants/verifications_conflicts_transfer_user.png[Transfer user form] .Transfer user form |=== @@ -27,7 +54,7 @@ image:verifications_conflicts_transfer_user.png[] |Reason |Required -|Why you want to transfer the user +|Why you want to transfer the user account |Email |Required @@ -35,4 +62,5 @@ image:verifications_conflicts_transfer_user.png[] |=== -After the user is transferred, both accounts (the original and the new one) will be merged. +After the user is transferred, both accounts, the managed one and the new one, is merged into one, that takes the +email address entered in the form, and the valid verification is transferred to this account.