Users & Permissions

By the end of this page everyone at home has their own account, their own phone notifications, and sees only the cameras they are meant to see.

Before you start

User management is a Pro feature and needs a Pro license, and only an admin can create accounts. Where: Settings → Users.

1. Create an account for a family member

1
Create it
Where: Settings → Users → "New user".
2
Fill in the basics
What to do: a username of 3–32 letters or digits (used to log in); an initial password of at least 8 characters with letters and digits; and a display name such as "Wife" or "Dad" — that is what event lists show.
3
Choose a role
What to do: pick "Member" for family — they can watch but cannot change settings. "Admin" can change everything, and one of those in a household is plenty.
4
Save
How you know it worked: the person appears in the user list, with "Cameras" showing "All" for now.

Ignore the "Wall display" entry in the list

If you use the big-screen interface connected to your TV, the list will contain an account whose role is "Wall display" — that is the device account the display creates for itself. It can see every camera but cannot change any setting, and its role and camera access are maintained by the system and cannot be edited here. Delete it and the display simply creates a new one at next startup.

2. Let them see only certain cameras

1
Open the access list
Where: open that person in the user list → the "Camera ACL" tab.
2
Tick and save
What to do: tick the cameras they may see and click "Save ACL". How you know it worked: their "Cameras" column in the user list changes from "All" to a number.

An unticked camera is invisible, completely

A camera that is not ticked is entirely hidden from them — no live view, no playback, no events, in the browser or in the phone app — and events from those cameras are never pushed to them either. This is also one of the most common reasons behind "they say they get no notifications". Admins implicitly have access to every camera and need nothing configured here.

3. Get notifications onto their phone

1
They sign in on the app once themselves
What to do: they sign in to the SkyView phone app with their own username and password.
2
Check the device is bound
Where: Users → open them → the "Linked devices" tab. How you know it worked: you can see the platform, the device and when it was last seen. If it is empty, they have not signed in on the app yet.
3
Send a test push
Where: the "Security & test" tab for that same person. What to do: click "Send test push". How you know it worked: it says "Test push sent to N device(s)" and their phone rings. This one bypasses quiet hours and mute.
4
Let them tune their own preferences
Where: they sign in to the web admin → Settings → My account → Push preferences. What to do: they choose their subscribed cameras, their subscribed events and their own quiet hours. Details in Notifications & Push.

A lost phone, or a new one

Click "Force revoke" under "Linked devices" and that device stops receiving pushes immediately; the next time they sign in on the app it binds again, so a new phone is unaffected.

4. Resetting a password

1
An admin resets someone else's
Where: Users → open that person → "Security & test". What to do: fill in "New password" and click "Reset password". The old password is not needed. After that: tell them the new password securely — not in a group chat.
2
Changing your own
Where: Settings → My account.
3
The admin cannot get in either
What to do: see "Forgot the password and cannot log in" in Troubleshooting — it takes one command on the machine running SkyView.

They can add a lock of their own

Anyone can go to Settings → My account → Sign-in security and turn on two-step verification, add a passkey, or link an external account to sign in with — three things an admin cannot do on their behalf, and there is no "require it for everyone" switch. When a family member loses their phone or has their authenticator wiped and cannot get in, the same "Security & test" tab has "Reset two-step verification", which puts them back: their password stays the same, their next sign-in needs the password alone, and they set a new phone up once they are in. See Two-Step Verification, Passkeys and Single Sign-On.

5. Disabling and deleting

Disable — the account and its data stay, they just cannot log in. Use this when the person is still around but should not have access for now.
Delete — also wipes their device bindings, push preferences and camera access, and cannot be undone.
The last admin cannot be deleted — at least one active admin has to remain, and the attempt is blocked with an error.

6. Common questions

They sign in and see no cameras at all — nothing is ticked in their camera access list.
They get no notifications — first check whether their phone is under "Linked devices", then work through the last section of Notifications & Push point by point.
I want them to see events but not live video — permissions are currently granted per camera: if they can see it, they get live, playback and events alike, with no finer split. To separate things, separate them by camera.
Creating a user says the username exists / the password is too weak — a username is 3–32 letters and digits and has to be unique; a password is at least 8 characters and must contain both letters and digits.

Notifications & Push — each person's own push preferences and quiet hours
Client Apps — how to sign in on a phone
Troubleshooting — what to do when you forget the password
Two-Step Verification — authenticator app, recovery codes, and how an admin resets them
Passkeys — sign in with a fingerprint or your face
Single Sign-On — sign in to SkyView with a Synology or work account

Was this page helpful?