Managing members from the front end

Portal members (end users of Xpand Portal who work with the front end) are normally created and managed in CMS. However, Xpand Portal also provides portal administrators with the ability to manage (create, edit, delete, send invitation emails, etc.) from the front end. To be able to do this, the corresponding page must be configured for your portal.

 

  Important

Some member settings are only available when managing members from the front end.

Setting up pages for managing members from the front end

Normally, pages for managing members from the front end is deployed during portal installation as part of the content package, and should already be available on your portal. In case they are missing, you can set them up using the details below.

To set up a grid page for managing members from the front end

  1. Create a grid page where portal administrators will be managing members from the front end. When creating the page, make sure the following grid settings are configured as described below:
    1. On the Data source tab, set the Entity setting to PortalMembers.
    2. On the Grid tab, under Fields, set up fields that will be available on this page. The recommended list of fields is shown below.
    3. On the Permissions tab, set up grid permissions. Make sure that only administrator member groups have access to this page. Under Toolbar commands add grid actions that you want to be available on the page. For this page, we recommend configuring the following actions:
      1. Select (to be able to select member records to perform actions with).
      2. Refresh (to be able to refresh data on the page without reloading the whole page).
      3. Create (to be able to register new members by creating new member records).
      4. Edit (to be able to edit information about members)
      5. Delete (to be able to delete members from the portal). 
      6. Export (to be able to export member information to Excel/PDF).
      7. Print (to be able print out member information).
      8. Filter (to be able to set filters on the page)
      9. Complex modify (to be able to invite new members by sending an invitation email). For this action, specify the following action settings:
        1. Caption = Send invitation email
        2. Show command title = Yes
        3. Command icon = (an icon that represents an envelop/email)
        4. Dialog window settings:
          1. Width = 4
          2. Items = [[membername]]
        5. Fields to update:
          1. Field = xSendConfirmation (PortalMembers)
          2. Value: Constant value = 1
  2. Select Save and publish to save the changes and publish them on the front end. Optionally, you can select Preview to preview how the page will look like in the front end.

If want to be able to view/edit members on a card (detail) page, also create a child detail page under the created grid page.

To set up a detail page for managing members from the front end

  1. Create a detail page as a child page for the created grid page (described above). On this page, portal administrators will be viewing/editing members as well as approve/reject member registration requests on on a detail page. When creating the page, make sure the following detail page settings are configured as described below:
    1. On the Data source tab, set the Entity setting to PortalMembers.
    2. On the Permissions tab, set up detail page permissions. Make sure that only administrator member groups have access to this page. Under Toolbar commands add detail page actions that you want to be available on the page. For this page, we recommend configuring the following actions:
      1. Save (to be able to save the changes).
      2. Complex modify (to be able to invite new members by sending an invitation email). For this action, specify the following action settings:
        1. Caption = Send invitation email
        2. Show command title = Yes
        3. Command icon = (an icon that represents an envelop/email)
        4. Dialog window settings:
          1. Width = 4
          2. Items = [[membername]]
        5. Fields to update:
          1. Field = xSendConfirmation (PortalMembers)
          2. Value: Constant value = 1
  2. Select Save and publish to save the changes and publish them on the front end. Optionally, you can select Preview to preview how the page will look like in the front end.
  3. Create detail page layout block(s) for hosting fields, and then add field sets to them. The recommended list of fields on the detail page is the same as on the grid page.

Managing members from the front end

If pages for managing members from the front end were configured, portal administrators can sign in to the portal using an admin member role (or any role that was configured to have access to the pages where members are managed), locate the page for managing members, view member information as well as perform various activities (depending on the actions that were configured):

  • Register new members (using the Create action)
  • Edit member information (using the Edit action)
  • Export member information (using the Export action)
  • Invite new members (using the Send invitation email action (the caption can be different in your case) configured on the basis of the Complex modify action as described above)
  • Delete members (using the Delete action)

Synchronization of members between back and front end

Members are automatically synchronized between back and front end; normally there's no need to perform any additional steps to synchronize member information. However, under certain circumstances, synchronization may fail due to various reasons. In this case, you can force sycnhronization of members as follows:

  1.  In CMS, go to Members.
  2. On the Members Export/Import tab, select the Synchronize members button to force member synchronization. 

Managing sign up requests

When members sign up on the portal, they submit a request to register a new member account for them. To be able to manage sign up requests, a grid page must be created for administrators on the front end.

 

  Note

For the sign up functionality to work correctly, also the Account registration page must be configured, and the ability to sign up must be enabled in the settings of that page. 

To create a grid page for managing sign up requests

  1. Create a grid page where portal administrators will be able to approve/reject sign up requests. When creating the page, make sure the following grid settings are configured as described below:
    1. On the Data source tab, set the Entity setting to PortalMemberRegistrationRequests
    2. On the Grid tab, under Fields, set up fields that will be available on this page. The recommended list of fields is shown below.
    3. On the Permissions tab, set up grid permissions. Make sure that only administrator member groups have access to this page. Under Toolbar commands add grid actions that you want to be available on the page. For this page, we recommend configuring the following actions:
      1. Select (to be able to select member registration requests to perform actions with).
      2. Refresh (to be able to refresh data on the page without reloading the whole page).
      3. Edit (to be able to edit member registration requests)
      4. Delete (to be able to delete member registration requests).
      5. A Complex modify action (for administrators to be able to confirm member registration requests). For this, specify the following action settings:
        1. Caption = Confirm
        2. Show command title = Yes
        3. Command icon = (an icon that represents confirmation/approval)
        4. Base dictionary key = XPortal.Frontend.ConfirmRegistrationRequest
        5. Dialog window settings:
          1. Title = Confirmation
          2. Height = 130
          3. Width = 4
        6. Validation filters:
          1. A filter where the filter logic is AND and  VerificationStatus (PortalMemberRegistrationRequests) = pending
          2. A filter where the filter logic is AND andMemberRoles (PortalMemberRegistrationRequests) != ___empty___
          3. A filter where the filter logic is AND anddatabaseName(PortalMemberRegistrationRequests) != ___empty__
        7. Fields to update:
          1. Field = VerificationStatus (PortalMemberRegistrationRequests)
          2. Value: Constant value = Confirmed
      6. Another Complex modify action (for administrators to be able to reject member registration requests). For this, specify the following action settings:
        1. Caption = Reject
        2. Show command title = Yes
        3. Command icon = (an icon that represents rejection)
        4. Base dictionary key = XPortal.Frontend.RejectRegistrationRequest
        5. Dialog window settings:
          1. Title = Confirmation
          2. Height = 130
          3. Width = 4
        6. Validation filters:
          1. A filter where the filter logic is AND and  VerificationStatus (PortalMemberRegistrationRequests) = pending | new
        7. Fields to update:
          1. Field = VerificationStatus (PortalMemberRegistrationRequests)
          2. Value: Constant value = Rejected
  2. Select Save and publish to save the changes and publish them on the front end. Optionally, you can select Preview to preview how the page will look like in the front end.
  3. Create detail page layout block(s) for hosting fields, and then add field sets to them. The recommended list of fields on the detail page is the same as on the grid page.

To manage sign up requests

  1. Sign in to the front end using an administrator member role (or any role that was configured to have access to the page where sign up requests are managed).
  2. Locate the page where sign up requests are managed.
  3. Review new sign up (member registration) requests.
  4. To confirm a member registration request, select the line with the request, and then select the Confirm action (the caption may be different in your case). When a request is approved, the member receives an email notification with further instructions (with a link to reset their password), while the administrator receives an email notification that a new member account has been registered. The email templates are configurable on the Account registration page.
  5. To reject a member registration request, select the line with the request, and then select the Reject action (the caption may be different in your case). When a request is approved, the member receives an email notification that their request has been rejected, while the administrator receives an email notification that a new member account has not been registered. The email templates are configurable on the Account registration page.