All topics
The network drive
Files and websites
Cameras and sensors
Network and questions
Device Accounts
A device account is the username and password another device signs in with: the credential for the network drive, for git, for protected websites and for camera feeds. There is no guest access, so every connection belongs to an account.
The first account
A fresh install has no accounts. The first time a device tries to sign in
to the network drive, the Share tab notices and offers to create that
account: the username comes from the attempt, the password is chosen on
the server. When a git client makes first contact instead, an account
named nasreborn with a strong generated password is created for it, so
the credentials a git app points you to always exist. Accounts live under
Settings → Sharing on the server; a password is revealed with
Face ID, Touch ID or the device passcode, and copies with a tap.
One account is all a solo user needs.
Accounts exist for revocation
A new account reads and writes everything the server shares. The first reason to create more than one is not permissions but revocation: each person (or each machine) gets a login you can revoke later without touching the others, and each account shows when it was last used, so a stale one is easy to spot. The free tier includes one account; more come with the Pro unlock, so each member of the household can have their own.
Narrowing what an account reaches
An account can also be limited to part of the server. On its screen, turn All content off and tick the folders, repositories and camera feeds it may reach. The list starts with everything that exists right now, so switching it off takes nothing away immediately; anything added later stays out until you tick it as well. One list covers every protocol at once, so there is no separate answer for the network drive, for S3, for git and for the web.
What an account cannot reach behaves as though it were not there: the share does not appear on the network drive and does not mount if it is typed in by hand, the folder is missing from S3 listings, and a repository or feed answers a plain 404. Nothing announces a refusal, since that would confirm what is being hidden. Changing an account's scope also disconnects sessions it has already mounted, because a network drive only checks the share name when it is first connected.
Narrowing is available on every tier: it can only ever take authority away from a credential, never add it.
Creating an account
In Settings → Sharing, tap Add Account. Usernames are short and lowercase
(letters, digits, . _ -).
Type a password or let the app suggest a strong one built from unambiguous
characters, made to be typed into a login sheet on another screen. The app
warns about weak passwords but the choice stays yours.
Git tokens
Once the server hosts a git repository, each account can also mint API tokens: long random strings that work in place of the password for git clients and scripts. Tokens are revocable individually, so a build machine can lose its access without the account changing its password.