Sign-in, users and roles
Argus has its own sign-in. Accounts live in the site database, with an email address and a password. There is no outside identity provider, so the site works without internet access.
Each site has its own users. An account on one site does not work on another.
Create the first admin account
The first time anyone opens a new site's dashboard, Argus asks for the first admin account.
- Open the dashboard address.
- On the first-time setup page, enter your Email Address and a password of at least 12 characters, twice.
- Click Create Admin Account.
You are signed in as an admin. Setup works only once, for the first account. After that, everyone goes to the sign-in page, and only an admin can add accounts.
Before you put a site into use, your administrator must set a long random SESSION_SECRET. Argus signs session cookies with it and refuses to start without a proper value. Never use a value copied from an example or another site. See Install.
Sign in and out
- Open the dashboard address.
- Enter your email and password, then click Sign In.
Email addresses are not case-sensitive when you sign in.
To sign out, click Logout at the bottom of the sidebar. Signing out ends the session on the site, so a copy of the old session cookie no longer works.
After repeated failed sign-ins from the same address, Argus refuses further attempts for a while. An account that gets many failed attempts from elsewhere is slowed down but never locked, so the owner can still sign in with the right password. Every sign-in, failed sign-in and sign-out is recorded in the audit log.
Roles
Argus has two roles.
| You can | Operator | Admin |
|---|---|---|
| See alerts, clips, captions and events | Yes | Yes |
| Watch the dashboard camera view and the Live Wall | Yes | Yes |
| Assign, acknowledge, resolve, dismiss and reopen alerts | Yes | Yes |
| Use the Copilot | Yes | Yes |
| See reports and export them as CSV | Yes | Yes |
| Scan the network for ONVIF cameras | No | Yes |
| See cameras, organizations and edge nodes | Yes | Yes |
| See camera user names and passwords | No | Yes |
| Add, change and delete cameras, zones and organizations, and test connections | No | Yes |
| Create and change detection profiles, event types, workflows and notification channels | No | Yes |
| Change retention settings | No | Yes |
| Add users, change roles, reset passwords and deactivate accounts | No | Yes |
| Read the audit log | No | Yes |
In the dashboard, operators don't see the Event Types, Workflows, Audit Log and Settings tabs.
Add a user
You need the admin role.
- Open Settings and pick Team Access.
- Click Invite Member.
- Enter the person's Email Address and a Temporary Password of at least 12 characters.
- Pick the Access Level (Role): Operator or Administrator.
- Click Provision Account.
- Give the person their password over a secure channel and ask them to change it.
The Team Access list shows every account with its role and the date it was added. Use Search users... to find one.
Manage users
You need the admin role. Open Settings and pick Team Access. Each account shows its role, its status (Active or Deactivated) and the date it was added. Your own row shows You: you can't change your own role or deactivate yourself here.
For every other active account you have three actions:
| Action | What happens |
|---|---|
| Make admin or Make operator | Changes the role. Confirm the change. The user is signed out everywhere and signs in again with the new role. |
| Reset password | Enter a new password of at least 12 characters, twice, then click Reset password. Give the user the new password over a secure channel. They are signed out of every browser. |
| Deactivate | Confirm the change. The user is signed out at once and can't sign in again. Their history, alerts and audit log entries stay. |
Every change is recorded in the audit log.
The last admin
A site always keeps at least one active admin. Argus refuses to make the last active admin an operator, or to deactivate or delete that account, and shows: "This is the last active admin account. Make another user an admin before removing this one's admin access." Make another user an admin first.
Sign a user out everywhere
To end every session of a user without changing anything else, for example after a lost laptop, use Sign a user out everywhere in the API. Resetting the password or deactivating the user in Team Access also signs them out everywhere.
Change your own password
- Click Change password in the sidebar.
- Enter your Current password, then the New password twice.
- Click Change password.
You stay signed in in this browser. Every other browser where you were signed in is signed out.
After 5 wrong current passwords within 15 minutes, Argus refuses further attempts for a while.
Password rules
New passwords must be at least 12 characters. This applies to new accounts, changed passwords, resets by an admin and resets by email. Accounts created before this rule keep working with their old password until it is changed.
Forgot your password
If the site can send email, you can reset your own password:
- On the sign-in page, click Forgot password?.
- Enter your Email Address and click Send reset link.
- Open the email and click the link. It works once, and for 30 minutes.
- Under Choose a new password, enter the New Password twice, then click Set new password.
- Sign in with the new password.
Setting a new password signs your account out of every browser.
The page always says the same thing: "If an account exists for that email address, a password reset link has been sent." It never tells anyone whether an address has an account. If the email doesn't arrive within a few minutes, check your spam folder. A newer link cancels older ones. If a link has expired or was already used, the page says so; request a new one.
To stop abuse, Argus limits how often reset links can be requested, and sends at most 6 reset emails an hour to one address.
If the site can't send email, the Forgot password? page says so and asks you to contact your administrator. An admin can then set a new password for you in Team Access.
Set up password reset email
Password reset by email needs two things: an address for the links, and a way to send mail. Until both are set, users who forget their password are asked to contact an administrator.
- The link address. Reset links point at
PUBLIC_BASE_URLin.env, for examplePUBLIC_BASE_URL=https://argus.example.com. If it is empty, Argus builds the address fromSITE_DOMAIN, or from the first name inSITE_HOSTSandHTTPS_PORT. Use the address users open the dashboard at. Argus never takes it from the request, so a forged request can't point a link at another site. - Mail transport. Pick one:
- In the dashboard, open Settings > Notifications, and under Account Emails pick an email notification channel in Send with.
- Or set the SMTP relay in
.env:SMTP_HOST,SMTP_PORT(default587),SMTP_USERNAME,SMTP_PASSWORDandSMTP_FROM. It is used when no channel is picked. The Send with list then shows SMTP relay from the server environment (SMTP_*).
When both are in place, the Account Emails card shows the address the links point to and how long they stay valid. Otherwise it says what is missing. Your administrator can change the link lifetime with PASSWORD_RESET_TTL_MINUTES (default 30).
The link carries its one-time code in the part of the address after #, so it never reaches a server log. Only a fingerprint of the code is stored on the site. Requests, completed resets and failed attempts are recorded in the audit log.
Sessions
When you sign in, Argus creates a session on the site and sets a cookie in your browser that only refers to it. The cookie is only sent over HTTPS.
- A session ends after 30 minutes without activity, and 12 hours after you signed in, whichever comes first. Your administrator can change both.
- Signing out, a password change or reset, a role change and deactivation end sessions on the site at once. A copied cookie from an ended session is refused.
- Argus checks your account on every request, so a change to your account takes effect right away.
The dashboard is served over HTTPS by default, so passwords and session cookies are encrypted on the network. See Install.