Record the current permissions and identify the precise failing operation. Common website defaults can differ by runtime and provider policy; broad write permission is not a substitute for correct ownership.

1. Open File Manager, select the domain and enter the directory containing the affected item.
2. Click its numeric value in the Perms column to open Change Permissions.
3. Set only the required owner, group and other read/write/execute choices. Directory execute means traversal, while a normal PHP source file usually does not need executable permission.
4. Apply the change and test the exact application action that previously failed. Confirm sensitive configuration remains inaccessible through a public request.
5. Document the change and return unnecessary write access to the previous restricted setting after an installation or maintenance task.

The application should perform its required action without granting unrelated users broad access. Inspect parent-directory traversal permissions if the file’s own mode appears correct.

Tiny File Manager’s documented control changes individual items and does not change user or group ownership. Ask the provider to investigate ownership or runtime identity where necessary. Do not recursively set the entire account to 777.

The process may run as another user, encounter a read-only location, hit a quota or be blocked by server policy. Diagnose the actual error instead of continually broadening permissions.

• Extracting an archive in SiteWorx Tiny File Manager
• Applying permitted PHP settings to one SiteWorx domain
• Following SiteWorx web-server logs during a reproducible error
• Changing a SiteWorx database-user password

• InterWorx: How To Change File Permissions In Tiny File Manager