Activate your account

Getting started with CP Word List takes three things: sign in with Google, accept the Terms and Privacy Policy, and enter your Cloudpath server address to activate the service.

1. Sign in with Google

Go to https://wordlist.lanpulse.com/dashboard/login and choose Sign in with Google. CP Word List uses your Google account for sign-in — there is no separate password to create. The email on your Google account becomes your tenant identity.

2. Accept the Terms and Privacy Policy

The first time you sign in, you land on a click-through screen. Check the box to accept the Terms and Privacy Policy, then continue. Your account is created only after you accept. Your acceptance is recorded with a timestamp.

Note

If the Terms or Privacy Policy are updated later, you’ll be asked to accept the new version the next time you sign in. Enrollments already running through your Cloudpath workflow keep working during that time.

3. Activate by entering your Cloudpath FQDN

A new account starts inactive. To activate it, open the dashboard and enter your Cloudpath FQDN (the hostname of your Cloudpath server, for example na1.cloudpath.net) in the Cloudpath Configuration form, then save.

What happens next depends on the server:

Cloudpath server	Result
Hosted — any *.cloudpath.net address (e.g. na1.cloudpath.net)	Approved automatically. The service activates as soon as you save a valid FQDN.
Self-hosted — any other hostname	Held for review. Your account stays pending until an admin approves it. Email cpwordlist@neuralconfig.com to request review.

While an account is pending, outbound calls to your Cloudpath server — both Test Connection and the live enrollment webhook — are disabled. Once approved (or auto-approved), they’re enabled.

Next steps

• Configure your Cloudpath connection — add your API credentials and SSID name, and grab your Tenant ID and Shared Secret.
• Add the enrollment workflow steps in Cloudpath.

If you don’t see the option to sign in, or your account stays pending after you’ve entered a hosted FQDN, see Troubleshooting.