Logging in is the first step to enjoying engaging content within Hubb. Have a user who can't find their invite? No problem. The Unaccepted Invites Report can help you find a unique invite that has been sent to a user.
The unaccepted invites report shows a list of all users who have been sent invites, but not yet accepted the invite and logged in to Hubb. Users who have accepted invites, and users who have not been sent invites will not appear on this report.
Locating The Report
|1. Navigate to the Admin portal|
|2. Select Reports in the left hand navigation|
|3. Expand the "Admin" heading on the reports page and select "Unaccepted Invites".|
|4. The report will load and display a list of all users who have been sent invites that are unaccepted.|
|5. After the report loads, it is best practice to press the 'Refresh' Button before downloading the report. This will ensure you are receiving the most accurate information.|
|6. After refreshing the report, select the 'Download' button:|
|7. Then choose the 'crosstab' option in the menu:|
|8. Lastly, click the 'Download' Button:|
Utilizing the Report
Now that you have the report downloaded, you can search for a specific user by name, or e-mail address.
Locate the user you are searching for, copy the full invite URL in column F, and provide it to the user. This will allow them to accept their invite, setup a password, and login to Hubb. For more information on accepting an event invitation please see this article.
Please note, that if a user has been sent multiple invites, each invite will appear under that user on the report. Always be sure to send the most recent invite, which is denoted in column G "DateCreated". Only the most recent invite sent to a user will be valid.
In the example below, you can see that "Pending Test" has two invite URLs. One was created on 5/29/2020, and the other 10/07/2020. In this case, we would select the invite URL that was created on 10/07/2020, and send this to the user.
Have any further questions? Shoot us an e-mail to firstname.lastname@example.org