Airbyte Icon
You add an airbyte icon by linking a vector file in your connector definition. The platform reads this graphic file and displays it in the user dashboard. Data teams build custom connectors to move rows between internal apps and warehouses. Engineers often use broad database roles to get these new connectors running fast. When a connector role has too much power, every sync job brings risk. How the airbyte icon and connector setup work Every data source and destination in the platform relies
Icon: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You add an airbyte icon by linking a vector file in your connector definition. The platform reads this graphic file and displays it in the user dashboard. Data teams build custom connectors to move rows between internal apps and warehouses. Engineers often use broad database roles to get these new connectors running fast. When a connector role has too much power, every sync job brings risk.
How the airbyte icon and connector setup work
Every data source and destination in the platform relies on a metadata file. This file tells the web app how to name and display the tool. When you add a custom airbyte icon, the web app loads that image. Users see this visual marker when they pick a source or destination.
Behind that visual marker sits a worker container that moves your data. The worker uses stored database keys to log in and read tables. Admins enter these keys into the web form during the initial setup. The platform stores those secrets and passes them to the worker at runtime. Each sync job spins up a worker, logs in, and pulls rows.
Managing credentials for custom connectors
Teams often create one shared database user for all their sync jobs. They give this user full read or write power across all schemas. This makes it easy to add new tables to a sync schedule later. Nobody has to ask a database admin to update grants for each table.
Still, shared keys create blind spots in your database audit logs. Every query from the data pipeline shows up under the same user name. If a developer runs a test sync from a local machine, it looks identical. You cannot tell which team member triggered a heavy read query. You also cannot separate automated pipeline runs from manual human queries.
What native connector roles solve and what they miss
Native database roles let you limit which tables a pipeline user can read. Workspace permissions in the data platform also limit who can edit a connector. These controls decide who can log in and start a sync job. They help you block unauthorized users from changing your pipeline schedule.
Icon: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, static roles do not inspect what individual queries do in flight. Once a worker or engineer logs in, the database trusts every command. A broad role allows someone to pull full tables with sensitive customer fields. Raw emails, phone numbers, and card numbers flow straight into the destination. Native setup rules cannot rewrite those matched fields in query results on the fly. They also cannot require a quick peer check before a risky command runs.
Add runtime guardrails and masking beside your databases and APIs
Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.
Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.
Frequently asked questions
What file format works best for a custom connector graphic?
Vector graphics work best because they scale cleanly on any screen size. Most teams use a square vector file with a transparent background.
Where does the platform display the connector graphic?
The web app shows the graphic in the source and destination catalogs. It also appears on active sync status pages to show data flow.
Why should teams avoid shared admin keys in data connectors?
Shared admin keys let any pipeline job read or alter every table. Using scoped roles and statement controls keeps sensitive fields like national IDs safe.
Teams that document these role rules and review logs each month catch config drift early. Clear ownership for each role keeps live systems simple to run and easy to audit across the whole team.