Account Access
Account Access covers the public sign-in, registration, and password-reset flows that lead into a NataPulse workspace.
Sign in
Section titled “Sign in”Enter the account email and password on the sign-in page. Invalid credentials and connection failures are shown inside the form. While a request is in progress, the form prevents a second submission.
An already authenticated user is sent into the product. Authentication alone is not a promise that every product surface is available.
Create an account
Section titled “Create an account”Self-service registration asks for first name, last name, email, and a password that meets the displayed minimum length. Successful registration starts the account session and opens Live Pulse.
The form reports cases such as an already registered email, invalid input, too many attempts, or a connection failure. It does not silently create a partial account when registration fails.
Reset a password
Section titled “Reset a password”The reset request accepts an email address and displays the same neutral success message whether or not an account exists for that address. This protects account privacy.
A valid reset link opens the new-password form. An invalid or expired link produces an explicit error and offers a path to request a new one. After a successful reset, sign in with the new password.
Return to requested page
Section titled “Return to requested page”If an active product session expires and a request is rejected, the product sends the user to sign-in and preserves the interrupted same-site path. Successful reauthentication can then return to that path.
An initial unauthenticated visit to a protected deep link does not preserve that destination. After successful sign-in, it opens Live Pulse.
Registration and password-reset completion use their own documented destinations; they do not promise to restore an unrelated browsing history.
Workspace and capabilities
Section titled “Workspace and capabilities”An account identifies the user. A workspace determines shared product context, and permissions determine which actions the user can take. Capabilities determine whether conditional surfaces or data layers appear for that workspace.
An account with no eligible NataPulse product access receives a clear access-denied state. A user can also enter the product while individual surfaces remain unavailable. See Onboarding, Settings, and Capability Availability.
Security practice
Section titled “Security practice”Use a unique password, keep reset links private, and open account links only from a trusted NataPulse page or expected email. Do not forward a reset link or reuse it after completion. If a request was not yours, do not complete it; return to sign-in and contact support through the official channel available to your account.