Home Getting Started First-run permissions and local network access

First-run permissions and local network access

Last updated on Jul 10, 2026

First-run permissions and local network access

When you open Phyn for the first time, the app may ask for permissions that help it discover your Jellyfin server, find Cast-enabled devices, send notifications, or save media for offline use.

You can use Phyn without granting every permission immediately, but some features work better when the matching permission is allowed.

Permission principle: Allow the permissions for the features you plan to use. If you deny a permission, you can usually enable it later in your device settings.

Local network access

Local network access lets Phyn look for Jellyfin servers and Cast-enabled devices on the same network as your phone, tablet, or computer.

Allow this permission if you want Phyn to:

  • Automatically discover a Jellyfin server on your home network.
  • Find AirPlay, Google Cast, or other local playback targets where supported.
  • Connect more easily to local devices without typing addresses manually.

If you skip or deny local network access, you can still type the Jellyfin server URL manually. Local discovery may not work until you allow the permission in system settings.

Notification permission

Notification permission lets Phyn show supported app notifications on your device.

Allow this permission if you want to use:

  • Phyn in-app notifications.
  • Jellyfin webhook notifications sent to Phyn.
  • Device-level alerts for supported notification events.

Notification setup may also require extra server configuration. In Phyn, the onboarding text points you toward the notification section in settings, where you can get a notification URL for the Jellyfin webhook setup.

Storage and downloads

Downloads need enough local device storage. Depending on platform behavior, Phyn may also need file or storage access to save, manage, or delete offline media.

If a download fails, cannot be deleted, or disappears unexpectedly, check available storage and whether the operating system has restricted app storage access.

Casting and device discovery

Casting depends on the device, operating system, network, target TV or speaker, and server playback compatibility.

If a Cast or AirPlay device does not appear:

  • Make sure both devices are on the same local network.
  • Disable guest Wi-Fi isolation if it blocks device discovery.
  • Check that Phyn has local network permission.
  • Confirm another app on the same device can see the casting target.
  • Wake the target TV, speaker, Chromecast, or Apple TV.

What to do if you denied a permission

Open your system settings, find Phyn, and enable the permission you need. The exact path differs by platform, but you are usually looking for Phyn under app permissions, privacy settings, notifications, local network, or storage.

After changing a permission, close and reopen Phyn. Some permissions may not take effect on the current screen until the app refreshes.

Which permissions matter most

Feature Permission or setting that can matter
Discovering a local Jellyfin server Local network access
Casting to local devices Local network access and network visibility
Receiving push notifications Notification permission
Jellyfin webhook notifications Notification permission, Premium access, and server webhook setup
Offline downloads Local storage space and download permission from Jellyfin
Support screenshots Screenshot attachment permission or system screenshot access, depending on platform

If Phyn still cannot find your server

Local network permission helps discovery, but it does not fix every connection problem. If Phyn cannot find or connect to Jellyfin, type the server URL manually and confirm that the same address opens in a browser on the same device.

A VPN, reverse proxy, firewall, DNS issue, or offline Jellyfin server can still prevent connection even when permissions are correct.

Related articles