How to get there: Click Settings in the sidebar → Authentication.
Authentication controls how users access your portal. Cookie consent, the privacy statement, and anonymization are on the separate Settings → Privacy page, also under People & access.
Choose which login methods are available on your portal:
In Login Methods, use Allow visitors to create an account to open or close registration. When registration is open, visitors can create an account from the login page.
Use Show login link in header and Show Sign up in header to choose which links appear at the top of your portal, then click Save in Login Methods. Hiding Sign up in the header does not close registration.
New portals show only Log in in the header by default. Existing portals keep their saved choices. If registration is closed, Sign up stays hidden even when its header option is on.
Use Single sign-on (SSO) to connect existing customer accounts. That guide covers Standard identification, verified server-signed tokens, the login button and secret rotation.
How to get there: Click Settings in the sidebar → Authentication tab → scroll to Microsoft 365 / Entra ID SSO.
Let your team sign in with their existing Microsoft 365 work account. Only people in your organization can use this sign-in method. Your Microsoft security rules still apply, including any extra sign-in checks. See the Microsoft 365 / Entra ID SSO setup guide.
When enabled, new sign-ups are held in a pending state until an admin approves them. You can also auto-approve users based on their email domain (e.g., approve everyone with an @yourcompany.com address).
Require users to verify their email address before they can post or vote. This helps prevent spam and fake accounts.
Make your portal visible only to logged-in users. Visitors who are not signed in will see a login page instead of your boards. This is useful for internal feedback portals or pre-launch communities.
Hide your entire portal behind a single shared password. Visitors are shown a password prompt before they can see any content; once they enter the correct password, a cookie lets them browse for 30 days without re-entering it. Admins are never prompted, they log in as usual.
Common use cases:
How it works
https://your-portal.example/?k=YOUR_PASSWORD. The visitor lands, the password is verified, and they are redirected to the clean URL with the cookie set. The password is never left in the address bar after that first hop.Notes
Temporarily block all access to your portal. When enabled, visitors see a maintenance message instead of the portal. Admins can still access the portal normally.
Open Settings → Privacy.
Show a cookie consent banner to visitors. Review your own analytics and integrations when choosing your privacy setup. See privacy information for portal owners.
Open Settings → Privacy.
Add a link to your privacy statement. This link appears on the login/signup page and in the cookie consent banner, letting users know how their data is handled.