1 Users, Permissions and Account Security

Sharing one file space across people relies on accounts and permissions — not on everyone using the administrator. This chapter covers the permission model, account lifecycle, and a few disciplines that measurably cut accident rates.

The Permission Model

Accounts come in two kinds: administrators hold every permission and manage users and system settings; regular users get itemized permissions — upload, download, delete, rename, share and so on. Itemized grants combine into real job needs: read-only finance directories, read-write project directories, free-upload-but-no-delete asset libraries. Permissions only grow — an account can only do more over time — so grant tight first.

Creating Accounts

Administrators open user management, fill in a username and initial password, and check the permissions to grant; operators can also run one command, e.g. lynxdrive-ctl user add zhangsan initial-pass, appending --admin for administrator rights. Deliver the password offline and remind the person to change it at first login.

Changing and Resetting Passwords

Users change their own passwords in account settings; forgotten ones can only be reset by an administrator via lynxdrive-ctl user passwd username new-pass. Keep at least one working administrator account at all times, and never lend it out.

Permission Assignment Advice

Grant least privilege by post: read-only for viewing jobs; upload and download for delivery jobs; add delete and rename only for those tidying directories; treat sharing separately and grant it only to people who truly deliver externally. More permissions mean higher odds of accidental deletion and leaks, and harder investigations.

The Account Lifecycle

Create on hire, adjust on transfer, disable on departure — each step needs an owner. Staff turnover is the main source of permission drift: an unclaimed project account becomes a back door within half a year. Review the account list quarterly and decide on long-idle accounts.

Guarding the Administrator Account

Log in as administrator only for operations, never for daily browsing. Use a long password distinct from other systems, and reset it face-to-face at handover. A compromised administrator account equals a compromised file space — that is the line to hold.