Skip to content

Commit

Permalink
Implement review feedbacks
Browse files Browse the repository at this point in the history
  • Loading branch information
paulinebessoles committed Nov 26, 2024
1 parent 17c2597 commit e8fac0d
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/en/modules/admin/pages/participants/authorizations.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ NOTE: Several authorizations are available by default, but you can also develop

== Enable / disable authorizations

To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask your administrator.
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].

Expand Down
2 changes: 1 addition & 1 deletion docs/en/modules/admin/pages/participants/impersonations.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Impersonations are only available when at least one authorization is enabled for
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.

To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask your administrator.
To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask your instance implementer.

image::participants/participants_impersonations_backend_list_no_auth.png[Administrators Impersonations panel with no authorizations]

Expand Down
12 changes: 9 additions & 3 deletions docs/en/modules/admin/pages/participants/verifications_conflicts.adoc
View file
Original file line number Diff line number Diff line change
@@ -1,9 +1,15 @@
= Verifications conflicts

A verification conflict can happen when authorizations are enabled, and some participants were impersonated.
A verification conflict can happen when authorizations are enabled, and some participants create several accounts

Check warning on line 3 in docs/en/modules/admin/pages/participants/verifications_conflicts.adoc

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('are enabled').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are enabled').", "location": {"path": "docs/en/modules/admin/pages/participants/verifications_conflicts.adoc", "range": {"start": {"line": 3, "column": 56}}}, "severity": "INFO"}
or get impersonated.

For instance:

. 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.

This can also happens with impersonations:

. 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

Expand Down Expand Up @@ -56,5 +62,5 @@ image:participants/verifications_conflicts_transfer_user.png[Transfer user form]

|===

After the user is transferred, both accounts, the managed one and the new one, is merged into one, with the
email address entered in the form.
After the user is transferred, both accounts, the managed one and the new one, is merged into one, that takes the

Check warning on line 65 in docs/en/modules/admin/pages/participants/verifications_conflicts.adoc

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('is transferred').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is transferred').", "location": {"path": "docs/en/modules/admin/pages/participants/verifications_conflicts.adoc", "range": {"start": {"line": 65, "column": 16}}}, "severity": "INFO"}

Check warning on line 65 in docs/en/modules/admin/pages/participants/verifications_conflicts.adoc

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('is merged').

Raw Output:
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is merged').", "location": {"path": "docs/en/modules/admin/pages/participants/verifications_conflicts.adoc", "range": {"start": {"line": 65, "column": 80}}}, "severity": "INFO"}
email address entered in the form, and the valid verification is transferred to this account.

0 comments on commit e8fac0d

Please sign in to comment.