Registration subject to approval allows a Springly administrator to require their approval before a visitor who has created an account on the organization's website can access their member area and the site's private content. It is configured in Website > Settings and theme and managed from Community > Contacts.
Prerequisites: having the Website module, having already created a website and a member area, and being a platform administrator.
- What is registration subject to approval for?
- How do you enable registration subject to approval?
- How does a visitor submit a registration request?
- How do you approve or decline a registration request?
- What are the limitations of this feature?
To create a member area first, see the article Create a member area (or intranet).
Registration subject to approval is different from membership requests subject to approval: Understanding and enabling membership requests.
What is registration subject to approval for?
Without approval, anyone who creates an account from your site's login page immediately gains access to their member area and the site's private content.
With registration subject to approval:
- the person can create their account from the login page;
- their account remains pending: they cannot access their member area or the site's private content;
- an administrator must approve their request before they can join the community.
Registration subject to approval lets you verify the information entered before granting access. It also helps you control the number of people registered in your community, and therefore your subscription quota.
You receive one email per week listing pending accounts. This email is not sent if all requests have already been processed in the meantime.
How do you enable registration subject to approval?
- Go to Website > Settings and theme.
- At the bottom of the page, in the Other site options section, click Sign-up page & Profile.
- Under "Create a sign-up page?", three options appear. Select Yes, with sign-up subject to approval.
- Choose the information requested when creating an account. These fields correspond to those defined in Community > Settings, described in the article Configure the information in your contact database.
- Click Save.
New account registrations on your website are now subject to your approval.
How does a visitor submit a sign-up request?
- On your website, the visitor clicks the Log in button, displayed at the top or bottom of the page depending on your settings.
- On the login page, they click Create an account.
- They fill in the fields defined in Website > Settings and theme > Sign-up page & Profile.
- They click Create my account. A message lets them know their request is pending approval.
The request then appears in your back office, under Community > Contacts.
To learn how to display a login button on your Springly website, see the article Add or remove the login button to the member area on your website.
How do you approve or decline a sign-up request?
- Go to Community > Contacts. A People pending approval section appears above existing contacts.
- Check the person or people concerned.
- Choose an action:
- Contact: send a message to the person, for example to request additional information;
- Approve: the person joins your community, gains access to their member area, and is counted toward the number of contacts in your subscription;
- Decline or archive: the request is not granted.
Before deciding, click the eye icon (Detail) to open the person's record and view the information they provided.
Validated persons are removed from the Persons Pending Validation section and appear among your saved contacts.
- Validation is manual: there are no automatic approval rules, such as filtering by email domain.
- The setting is site-wide: it is not possible to require validation for access to specific private pages only.
- The notification email frequency (weekly) cannot be changed.
- Enabling the option applies to new requests only: existing accounts remain active.
- ⚠️ A validated person is not recognized as a member. This feature is distinct from membership requests, described in the article Understanding and enabling membership requests.
Comments
0 comments
Article is closed for comments.