vw_small

commit 4fae1e4298490b3ee9bda9bd97d0469217e64807
parent ff8eeff995d9ddd7f64cb610453f43470c3eefef
Author: Miroslav Prasil <miroslav@prasil.info>
Date:   Tue, 18 Sep 2018 11:49:20 +0100

Update the Invitation workflow documentation

Diffstat:
M
README.md
 | 
4
+++-

1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -441,7 +441,9 @@ We use upstream Vault interface directly without any (significant) changes, this
 
 ### Inviting users into organization
 
-If you have [invitations disabled](#disable-invitations), the users must already be registered on your server to invite them. The invited users won't get the invitation email, instead they will appear in the interface as if they already accepted the invitation. (if the user has already registered) Organization admin then just needs to confirm them to be proper Organization members and to give them access to the shared secrets.
+The invited users won't get the invitation email, instead all already registered users will appear in the interface as if they already accepted the invitation. Organization admin then just needs to confirm them to be proper Organization members and to give them access to the shared secrets.
+
+Invited users, that aren't registered yet will show up in the Organization admin interface as "Invited". At the same time an invitation record is created that allows the users to register even if [user registration is disabled](#disable-registration-of-new-users). (unless you [disable this functionality](#disable-invitations)) They will automatically become "Accepted" once they register. From there Organization admin can confirm them to give them access to Organization.
 
 ### Running on unencrypted connection