# Book Isle shared-library read-only check: verify access with a reader account

Language: en
Canonical: [Book Isle shared-library read-only check: verify access with a reader account](<https://allluckly.cn/en/guides/nasbook-shared-library-readonly-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-shared-library-readonly-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-shared-library-readonly-check/>)
Published: 2026-10-27T00:00:00+08:00
Modified: 2026-10-27T13:09:53+08:00
Author: Bison

Check catalogue, download and reading access with an intended shared-library reader account, separating local metadata, server write rights and WebDAV record sync.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-shared-library-readonly-check/>), translated on 2026-10-27. Original publication dates, attribution, code and version notes are retained.

An established shared library can use a scoped reader account without server-administration rights. Verify its actual catalogue and reading capabilities separately from local edits and remote writes. A read-only book source and a writable reading-data sync directory are distinct objects.

## Define the intended shared scope

Record expected folders, acquisition rights and reading-only intent from the authorised configuration. Compare with the same reader identity, not an administrator total. Use a readable sample and an out-of-scope directory only as a visibility boundary, without bypass attempts or copying credentials into notes.

## Inspect the catalogue under that identity

Open the existing connection and verify identity and edition, comparing another client with the same account. Directory visibility need not imply file access. Check identity/scope before broadening shares. App feature entitlement remains separate from server permission.

## Verify acquisition and body reading

Test beginning, middle and end through the supported access flow. Record acquisition failures without replacing the reader with administrator credentials. Verify permitted downloads offline, or document online-only limits. Use a known-readable EPUB/PDF baseline so format-management limits do not confuse permission checks.

## Confirm read-only policy at the server

Do not prove read-only access by deleting important books. Inspect server policy and, only if appropriate, use an approved disposable test area; otherwise state that only configuration and reads were checked. Button visibility alone does not establish remote write behaviour. Keep policy evidence separate from observed client actions.

## Separate local metadata from originals

Local labels, status and notes concern personal records and should not automatically be described as edits to shared originals. Inspect actual scope on the sample and identify changed layers. Personal ratings are not shared judgements, and deliberate server metadata work belongs in its authorised management flow.

## Check sync-directory writes separately

Reading-data WebDAV sync is distinct from acquiring books. Use a deliberately managed records destination rather than treating the shared-library root as the necessary sync target. Verify each task separately without indiscriminate permission expansion. Sync success does not establish uploading original books to an app-operated server.

## Keep scope and sample results

Record date, connection, account scope, sample results and the policy evidence without secrets. Recheck after device or scope changes. Unexpected visibility needs server-side review rather than relying on hidden app lists. Previously obtained local files have separate device access and are not assumed erased by later server restrictions.

## Acceptance and limits

Finish with expected visibility, readable samples, understood download rights and separated local/remote scopes. Destructive tests are unnecessary and unperformed checks should be stated. Investigate mismatched sync destinations separately. This workflow does not claim a complete server-security audit or account-isolation proof.

## Related guides and sources

[Connect Book Isle to WebDAV: download a book from a private library](<https://allluckly.cn/en/guides/nasbook-webdav-library/>); [Book Isle WebDAV sync: continue reading records across two devices](<https://allluckly.cn/en/guides/nasbook-webdav-sync/>).

Checked on October 27, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6766198898&country=cn>) lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6766198898>) and controls depend on the installed version. This article describes a personal reading or library-checking workflow without claiming step-by-step physical-device or private-server testing. Book files and reading records are managed separately; development recognition, generation or automatic analysis is not treated as released functionality.