User Activation and Login
To access Paragon Automation Web GUI, you must have an account in Paragon Automation. Your account is activated after you log into the Paragon Automation Web GUI. You can then perform activities as defined by your role.
If single sign-on (SSO) is enabled, you can access Paragon Automation through your identity provider (IdP) account. IdP authenticates your access privileges in Paragon Automation. For more information, see Single Sign-On.
The system administrator who installs Paragon Automation is usually the first user to log in by using the e-mail address and password entered while installing Paragon Automation. Once logged in, the system administrator creates an organization and is assigned the Super User role in the organization. A superuser can add or invite users to the organization.
Depending on whether SMTP or local authentication is configured, Paragon Automation sends invitations and notifications to users. See Configure SMTP Settings in Paragon Shell for information about the behavior when either or both local authentication and SMTP are enabled or disabled.
If SMTP is configured in Paragon Automation, an invitation is sent over an e-mail when the superuser invites users to an organization. A user can click the link in the e-mail invitation and complete the login tasks. Your login procedure depends on whether you are an existing user with a Paragon Automation account or a new user without a Paragon Automation account.
If SMTP is not configured in Paragon Automation, the Super User adds users to an organization and shares the Web URL of Paragon Automation and credentials (e-mail ID and temporary password) to log in, with the users. Users can then access the Web URL and log in using the credentials. Once logged in to Paragon Automation, the user is prompted to create a new password.
After the user logs in and accesses an organization, the first page that Paragon Automation displays depends on your user role. If your role is Installer, the first GUI page you view is the Onboard a device page. For users with other roles, Paragon Automation displays the Troubleshoot Devices page.
The log in procedures for different roles are as follows:
Log into Paragon Automation for the First Time After Installation
The first user to log into Paragon Automation is typically the system administrator who installs Paragon Automation. On successful installation, the system administrator gets the URL to access the Paragon Automation Web GUI from Paragon Shell. The Welcome message that appears after logging in lists the IP address and e-mail ID to access the Paragon Automation Web GUI.
To log in as the first user:
Log in as a New User Without an Invite (when SMTP is not Configured)
When SMTP is not configured in Paragon Automation, the superuser who creates your account in an organization manually informs you about the Web URL and the credentials (e-mail address and temporary password) to log into the Paragon Automation Web GUI.
To log in as a new user without an invite:
Log in as a New User for the First Time Without an Invite (when SMTP is Configured)
To access Paragon Automation Web GUI as a first-time user without an invite, you need the Web URL of Paragon Automation. To access the Web GUI, you must create an account in Paragon Automation. You will then receive a verification e-mail to validate your account.
To log in as the first user without an invite:
Log in as a New User With an Invite (when SMTP is Configured)
If SMTP is configured in Paragon Automation, you receive an e-mail invitation when the superuser creates an account for you to access an organization. You are also notified when your user account is modified.
To log in as a new user with an invite:
Access a New Organization (when SMTP is Configured)
To accept an invite to a new organization as an existing user already having an account in Paragon Automation, click the organization-name in the e-mail body. The Troubleshoot Devices (Observability > Health > Troubleshoot Devices) page of the organization opens in a browser.
The tasks you can perform in this organization depends on your user role. See Predefined User Roles Overview for more information.