"Request an Invite" is a link that can appear on your login page for people who don't have an account yet. Instead of letting anyone register on their own, it lets them submit their email address and asks an admin to add them manually. This article covers the settings that control it, the sequence of what happens when someone uses it, and the current limitations you should plan around.
How It Works
Two separate settings control this feature, and both matter:
| Setting | Where it lives | What it controls |
|---|---|---|
| Self-Registration | System Setup > Access > Security/Authentication | Whether "Request an Invite" appears at all. Turning Self-Registration off (closed registration) is what makes the link show up. |
| Unified Login | Site Setup > Beta | Required in addition to the above if users log in directly at an initiative URL. Without it, "Request an Invite" will not be available on an initiative-level login page, even if Self-Registration is off enterprise-wide. |
A third setting, the initiative's own Registration mode (Self Registration vs. Admin Invite Only), determines whether that specific initiative is open for sign-up, separately from whether the request link is available.
Steps
1. Turn off Self-Registration at the enterprise level
Go to System Setup > Access > Security/Authentication. Turn off Self-Registration. This enables closed registration, which is what makes the "Request an Invite" link appear at the bottom of the login box.
2. Enable Unified Login for initiative-level logins
If your users log in directly at an initiative URL rather than your main enterprise login page, go to that initiative's setup and enable Unified Login. Skipping this step is the most common reason the link doesn't show up even after Self-Registration is turned off.
3. Set the initiative's Registration mode
Under the initiative's Registration Settings, choose Admin Invite Only instead of Self Registration if you want that specific initiative closed to open sign-up.
4. Confirm the required registration emails are turned on
In Pipeline Setup > System Email Messages, make sure the Request Registration email, the registration confirmation email, and the Registration Request email are all enabled. If your team has disabled all system emails at some point and only re-enabled some of them, these are easy to miss. If they're off, the request flow can hang or error out for new users without any clear explanation.
Verify It Worked
Test with a brand-new email address that has never had an account on your site. Existing accounts and admin accounts will always succeed and can hide a broken flow, so testing with your own login won't catch this.
What Happens When a User Clicks "Request an Invite"
- A user without an account visits the login page.
- They see the "Request an Invite" link (the label is editable if you've customized it).
- They click it and are prompted to enter their email address.
- They submit the form.
- An email notification is sent to your Affiliate Sponsor.
-
The Sponsor reviews the request and manually adds the user to the system. There's no automatic add and no pre-filled "Add User" link in the email, so this step is manual every time.
Important Limitations to Know Before Enabling
- Only the Affiliate Sponsor is notified. There's currently no way to route this notification to a different admin or to multiple people.
- The email notification can't be customized. There's no template you can edit for this specific alert.
- Requests aren't stored anywhere in the platform. If the Sponsor misses the email, there's no dashboard or list to check later. The request is effectively gone.
- There's no "deny" option. The only way to turn down a request is to not act on it.
- This form isn't authenticated and has no built-in spam protection. Because anyone can submit a request without logging in, it can be targeted by automated or bulk spam submissions. If you notice an unusually high volume of "invite" requests, especially ones that look automated, contact Brightidea Support. This may be a sign your instance needs additional protection enabled at the system level.
Comments