...
| Code Block |
|---|
From: "groupersystem@gmail.com" <groupersystem@gmail.com> <-- note, this is configurable in grouper.properties To: someone@someschool.edu Sent: Sun, November 28, 2010 10:01:31 AM Subject: TEST:user1@school.edu has registered <-- in non prod env's a prefix can be specified in grouper.properties Hello, This is a notification that user user1@school.edu from email address person@yahoo.com has registered with the identity management service. They can now use applications at this institution. Regards. |
sda
Invite by entering in user id's
If you think your users will know the exact user ID of who they want to invite, you can enabled invites by user id's. The user will have the choice of inviting by email address or user id.
Set this in the media.properties:
| Code Block |
|---|
#if we should allow invite by identifier
inviteExternalMembers.allowInviteByIdentifier = true
|
Then the invite screen has that option
...
...
If you invite by login ID, then you will see all the results when clicking submit (nothing is emailed to the user)
...
...
sdaf
Invite view
Note that invites are stored as attributes on a stem, there is no dedicated table for them, but there is a view so you can easily see which invites are pending. Note once an invite is clicked on form the email, it is processed and deleted.
...