# iCouldPlay server account scope: distinguish restricted access from an empty library

Language: en
Canonical: [iCouldPlay server account scope: distinguish restricted access from an empty library](<https://allluckly.cn/en/guides/icouldplay-server-account-content-scope/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-server-account-content-scope/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-server-account-content-scope/>)
Published: 2026-10-27T00:00:00+08:00
Modified: 2026-10-27T13:09:52+08:00
Author: Bison

Compare catalogue, details and playback with the same account and verify intended personal library access.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-server-account-content-scope/>), translated on 2026-10-27. Original publication dates, attribution, code and version notes are retained.

An administrator seeing a film does not establish access for another account on a phone. Media servers can restrict libraries by account. Use your own authorised service to compare catalogue, details and playback, rather than expanding every permission or treating an empty page as deleted content.

## Define the account and intended scope

Record the account and a small expected sample set, respecting the intended family member's permissions rather than assuming administrator scope. Keep only necessary identifiers, without passwords or private-library uploads.

Retain an allowed clip and a deliberately restricted test location. The goal is agreement with intended rules, not universal access. Correct restricted behaviour may be invisibility or denied access depending on the service.

## Establish a same-account server reference

Log into the same server instance through its own interface or suitable client using the ordinary account. Compare libraries and samples. Authentication success alone does not validate catalogue, details and file retrieval.

If the source interface lacks allowed content too, investigate account scope, selected library and server indexing before app indexes. Nonadministrators should provide a specific observation to an authorised operator, without guessing accounts, sharing passwords or disabling authentication.

## Check catalogue identity in iCouldPlay

Verify address and account, then distinguish explicit errors, empty results and partial lists. Clear search or category restrictions and inspect the correct library, including separate film and series views.

Open sample details and check title, year, episode and source. Wrong artwork can mislead identity checks. An old matching card viewed by another account does not establish current permissions; retain source evidence beyond familiar covers.

## Verify actual content retrieval

Play allowed samples at beginning, middle and end. A visible title does not prove retrieval. Investigate read scope, returned paths, processing and applicable app entitlement separately from server account permissions.

Check restricted test results without bypassing them. Unexpected access calls for reviewing server configuration, without treating it as content supplied by the app. Limited success does not validate every library, account or file format.

## Recheck deliberately after permission changes

An authorised operator can change one documented scope value and compare the server interface before refreshing or reentering the app. Cached lists, sessions and service updates need not change simultaneously. Avoid many permission changes at once.

Preserve positions and connection information before any required login renewal, reading actual scope. Connection removal, file deletion and sign-out are different actions. Independently retained local copies need separate management; changed remote access does not automatically remove device files.

## Record the final scope matrix

List account, visible libraries, detail access and sample playback, including whether the restricted test behaved correctly. Add date, server type and app version and retain unknowns rather than generalising administrator success to all users.

Completion means intended scope agrees across server and client, allowed samples play and restrictions hold. Record last success and first failure for remaining differences. Distinguish authentication, catalogue, files and local copies for reliable private-library maintenance.

## Related tutorials and sources

Continue with [Emby connection basics](<https://allluckly.cn/en/guides/icouldplay-emby-library/>), [Jellyfin connection basics](<https://allluckly.cn/en/guides/icouldplay-jellyfin-library/>).

Checked on October 27, 2026 through [Apple's public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn>): iCouldPlay 1.1.0 requires iOS / iPadOS 13.0 or later. Feature scope follows the [official App Store listing](<https://apps.apple.com/cn/app/id6755653178>). This article describes a workflow and checks, without treating development-only controls as verified public features or claiming step-by-step physical-device or private-server testing. Follow the options in your installed version.