Filecatalyst Brand
To set up a custom filecatalyst brand portal, upload your logos and styles in the admin settings. This change updates the web portal so users see your company look during file transfers. Many IT teams use this setup to share large files with outside partners. Still, teams often pairs this visual setup with broad folder roles. Broad roles let users read or write more data than they should. How the filecatalyst brand architecture works A custom portal sits on top of a fast file transfer server.
Brand: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To set up a custom filecatalyst brand portal, upload your logos and styles in the admin settings. This change updates the web portal so users see your company look during file transfers. Many IT teams use this setup to share large files with outside partners. Still, teams often pairs this visual setup with broad folder roles. Broad roles let users read or write more data than they should.
How the filecatalyst brand architecture works
A custom portal sits on top of a fast file transfer server. Admins change the look and feel by adding custom images and colors. They also change the text on the login screen and email alerts. These visual updates help outside users trust the transfer portal when they log in.
Under the visual layer, the server manages user accounts and storage folders. Admins link the server to an active directory or create local user accounts. Each user gets a role that points to a specific folder path. When a user logs in, the system checks their name and password. Then the portal shows the custom look and loads the allowed folders. Users can upload or download large datasets over UDP network links. The server writes basic logs for each start and stop event.
What native branding solves and where gaps remain
The native portal setup solves trust and usability problems for partner teams. Clients see a familiar company logo when they send or read large files. The admin panel also handles basic folder mapping and bandwidth limits well. It decides who can log in and which root folder they can open.
Still, the native setup leaves a major security gap during active sessions. Folder roles only check who logs in at the start of a session. They do not inspect what individual commands or queries do in flight. Also, admins who run the server often share high-level system keys. If an engineer logs into the backend host to fix a transfer issue, they have full root control. A broad admin role lets a user read raw files or change server rules without approval. Native transfer logs show file names, but they miss host-level admin actions. They also cannot mask sensitive fields like emails or card numbers inside data queries.
Brand: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
How to tighten roles around file transfer hosts
Teams need better control over the hosts and databases that support file portals. Start by removing shared admin accounts on the transfer servers. Give every engineer a unique login tied to your main identity provider. Next, split folder roles so partner users can upload files without reading older archives. Review your server logs every week to spot strange login times or failed checks.
You should also separate portal style tasks from backend system tasks. Let web teams update logos without giving them full shell roles on the host. When an engineer must run a command on the server, require a peer check first. Also, apply data masking rules when teams query transfer metadata tables. Masking rewrites matched fields like phone numbers or national IDs in query results. This step keeps private user details safe during daily support work.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Does changing the portal look affect file transfer speeds?
No, custom logos and styles only change the web page layout. The core transfer engine still uses the same UDP network protocol for fast uploads.
Can we assign different visual themes to different partner groups?
Most enterprise transfer tools let admins map custom themes to specific user groups. You can check your admin manual to set up group-level portal views.
Why do we need extra controls beyond native folder permissions?
Folder rules only block unauthorized users at the login screen. They do not control what backend admins run on the host or mask private data in flight.