Skip to content

Users, roles and camera access

Aperture has two roles: administrators, who manage the whole system, and viewers, who watch the cameras you assign to them. This page covers the first administrator, adding and changing people, disabling and removing accounts, and the tamper-evident activity log.

On a fresh install the web app opens with Welcome to Aperture and asks you to create the administrator account.

  1. Enter a Name, an Email and a Password of at least 8 characters, and repeat it under Confirm password.
  2. Click Create account. You are signed in straight away.

The email address is your sign-in name. Aperture stores it in lower case, so Alex@example.com and alex@example.com are the same account.

This screen exists only while there are no accounts at all. Once the first one is created, the setup endpoint (POST /api/v1/setup) answers 409 already configured.

Administrator Viewer
Cameras All cameras Only the cameras ticked under Camera access
Live view, playback, alarms Yes For their cameras
Download clips, timelapse exports, share links Yes For their cameras; share links for their own clips
Own notifications, preferences, password, two-factor, passkeys Yes Yes
Add, change or remove cameras, zones, schedules, storage, detection Yes No
Remove footage Yes No
Users, Integrations, Automations, Activity Log Yes No (not shown)
Install and manage extensions; backup, restore, restart Yes No

A viewer’s camera list is the whole world for that account. Cameras that are not assigned do not appear anywhere: not on the dashboard, in Playback, in Alarms, in the change feed, in notifications or in extension panels. The Devices page shows their cameras as a read-only overview.

Viewers can:

  • watch live video and play back recordings of their cameras,
  • see the events of those cameras under Alarms,
  • download clips and timelapse exports of their cameras, and create share links for clips they made themselves (see Export and share),
  • set up their own notifications under Settings › Notifications,
  • manage their own password, two-factor authentication, passkeys and signed-in devices under Settings › Security (see Passwords, two-factor and passkeys),
  • use extension panels, which are capped by the viewer’s own permissions, never the installer’s (see Extension security).

Viewers cannot change any camera, recording, storage, detection or integration setting, cannot remove footage, and cannot read the activity log. The Users, Integrations, Automations and Activity Log entries are hidden from them, and opening those addresses directly sends them back to the dashboard. The server enforces the same limits on every API request, so hiding the pages is not the protection.

  1. Open Users in the navigation rail. On a phone, open Settings › General and choose Users under Administration.
  2. Click Add user.
  3. Enter the Email the person signs in with and, optionally, a Name.
  4. Choose the Role: Viewer or Administrator.
  5. For a viewer, tick the cameras they may see under Camera access.
  6. Click Add user.

Aperture generates a temporary password and shows it on the Account created card, together with the sign-in address and the email. From there you can:

  • Download card saves the card as a PNG image,
  • Print opens it in a print dialog,
  • Copy password copies only the password.

The password is shown once. When you click Done it is gone; Aperture keeps only a bcrypt hash of it. If you lose it before handing it over, open the user and set a new password (see Change a user).

The temporary password is 16 random characters in four groups of four, such as Abcd-Efgh-Jkmn-Pqrs. It avoids characters that are easy to misread (0, O, 1, l, I).

Through the API you can set the initial password yourself by sending a password (at least 8 characters) with POST /api/v1/users. The person is still asked to choose their own at first sign-in.

When the new user signs in with the temporary password, Aperture shows Set your password before anything else:

  1. They enter a New password of at least 8 characters, repeat it under Repeat password, and click Set password. The current password is not asked for at this step.
  2. Secure your account offers Passkey and Authenticator app. Either can be added now, both, or neither with Skip for now. A passkey needs HTTPS or localhost; on a plain-HTTP address the option is greyed out.

Setting the password also signs out any other browser that used the temporary one. Two-factor and passkeys can be added any time later under Settings › Security.

Click a user in the list to open Edit user. You can change the Name, the Role, the Camera access of a viewer, set a New password (leave it blank to keep the current one) and switch Disabled. Click Save changes. The email address cannot be changed.

  • Role and camera changes apply at once. Aperture reads the role and camera list from the database on every request, so the person does not need to sign out, and their API tokens follow the new limits too.
  • Switching a viewer to Administrator clears their camera list, because administrators see every camera.
  • Setting a new password signs the person out on every device. It does not make them choose their own at the next sign-in (only a person who has not finished their first sign-in is still asked), and their authenticator app stays turned on.
  • Two people editing the same user: if the user changed since you opened the dialog, the save is refused and Could not save the user. appears. Close the dialog, open the user again and repeat the change.

Turn on Disabled (“Prevent this account from signing in”) and save. Aperture then:

  • signs the account out on every device at once,
  • forgets every trusted device of the account,
  • refuses password, passkey and single sign-on sign-in for it,
  • stops accepting its API tokens,
  • revokes every share link it created, so the links stop working at once (the person sees them as expired with “revoked”),
  • stops its notifications: its rules deliver nothing while it is disabled, on any channel.

Nothing else is deleted. Turn Disabled off again to restore the account; its revoked share links stay revoked. The switch is not offered on your own account.

Click Delete, then Delete user to confirm. This is permanent. It removes the account together with its camera access, sessions, trusted devices, API tokens, share links and preferences. You cannot delete your own account.

The app lists only your own share links. An administrator can list another person’s links, or everyone’s, through the API: GET /api/v1/shares?user=<id> or ?all=true.

Nothing stops you from changing your own role to Viewer, even when yours is the last administrator account, and nothing in the app can reset another person’s authenticator. Keep two administrator accounts, or know the recovery path in Recover a locked-out administrator.

The activity log records sign-ins, setting changes, deletions, exports and shares. Open Activity Log in the navigation rail (administrators only).

Each entry has a time, the user’s email, the action, its target and a detail, plus the IP address and browser that made the request. The table shows Type, Event, Description, User, Severity and Date / Time.

What is recorded, among others:

Area Actions
Sign-in Successful sign-ins with the method (password, password, trusted device, 2fa, passkey, sso), failed sign-ins with the reason, sign-outs
Account security Password changes, two-factor turned on or off, passkeys added or removed, devices signed out
People and access Users created, changed and deleted; API tokens created and revoked; single sign-on settings
Cameras and recording Cameras added, changed, deleted, tested; zones, groups, picture settings; footage removed
System Storage, detection, site, weather and integration changes; backup, restore, restart, purge, reindex
Footage leaving Clip exports and downloads, share links created and revoked, and every time a share link is opened (logged as public)

The left side filters by severity (Info, Change, Removal, Failure), by time range (1D to All), by Types, by Action and by User (part of an email address), and the search box matches any text in an entry.

The page loads the newest 500 entries that match the Action and User filters; the other filters work within those. To read further back, use the API (below).

The log is never pruned automatically, and it is not part of a configuration backup.

Every entry stores a SHA-256 hash over the previous entry’s hash and its own time, actor id, action, target and detail. Editing or deleting an entry in the middle breaks every hash after it.

Under Integrity, click Verify chain. Aperture recomputes the whole chain from the first entry and shows Chain intact or Chain broken.

Be clear about what this proves:

  • It detects entries that were edited or removed from the middle of the log.
  • It does not detect entries removed from the end, and it cannot stop someone with write access to the database from rewriting the whole chain. There is no external anchor or secret key.
  • The actor email, IP address and browser are stored with each entry but are not part of the hash.
  • The IP address is taken from forwarded headers. See Client addresses behind a proxy for how to make it trustworthy.

Both endpoints need an administrator and, for a token, the system:read scope.

Terminal window
# Newest entries; filter by action prefix and by user, times in unix seconds
curl -s -H "Authorization: Bearer apt_…" \
"https://nvr.example.com/api/v1/system/audit?action=auth.&actor=alex&limit=200"
# Check the chain: {"intact":true,"firstTamperedId":0}
curl -s -H "Authorization: Bearer apt_…" \
"https://nvr.example.com/api/v1/system/audit/verify"

The list returns {"entries": […], "actions": […]}, newest first. Page with the X-Next-Cursor response header (see The API and tokens). limit defaults to 200; a value above 500 is treated as 500.

Related: Passwords, two-factor and passkeys, Single sign-on, Security model and hardening.