Separate building from source setup
Teammates with the product role can work on tools. Engineering-level permissions are needed to configure sources, while tenant roles control access to the wider workspace.
Governed data access
More people building.
Clearer data boundaries.
Let operations and customer teams shape the apps they need. Engineering defines the data sources, environments and credentials those apps can use, keeping access decisions close to the people responsible for them.
“Build the dashboard in a development environment first. Review it before binding the approved production reporting source.”
Working preview
A deliberate route to real data.
- Configure
- Source + credential permissions
- Select
- Development, staging or production
- Review
- Production-risk acknowledgement
A new app, shaped around your team’s work.
Start somewhere useful
Small enough to start.
Useful enough to matter.
Choose an environment deliberately
Organise sources by data environment and bind the app or conversation to the selected one. Production-risk source creation and binding require explicit acknowledgement.
Keep the scope in the database
Use credentials with only the permissions the tool needs. For a reporting app, that can mean a read-only database account and restricted views prepared by engineering.
A practical way forward
From the first request
to a shared decision.
Define the useful minimum
Agree the business question, the data needed to answer it and whether the tool needs to write anything. Avoid granting broader access just to speed up the first draft.
Configure the boundary
Engineering registers the supported data source, its environment, transport settings and credentials. Stored passwords are encrypted; the runtime receives the configuration needed for its bindings.
Review the app and the access
Test the tool using an appropriate environment. Check the data it exposes, acknowledge production risk when binding production access and follow your organisation’s review process.
How your team stays in control
A framework for governance. Decisions stay with your team.
Flex provides roles, environment bindings and protected credential handling. Your database grants and the finished app’s implementation determine the data people can read or change.
Explore Flex security- Choose database grants and views that limit the data scope.
- Enforce row-level policies in your database and app where needed.
- Review the tool’s authentication, authorisation and data exposure.
Before you start
Good questions.
Clear answers.
Which sources are supported here?
Flex’s configured database-source workflow supports PostgreSQL and ClickHouse. Engineering registers the source for a data environment and binds it to the relevant app or conversation.
Are production credentials pasted into a prompt?
Use the source-configuration workflow for credentials. Stored source passwords are encrypted and runtime bindings supply the access needed by the app. Do not put credentials into prompts or source code.
Does production acknowledgement replace approval?
No. It makes the risk explicit in the source and binding workflow. Your organisation still decides who can approve access and which review steps a tool must pass.
Start with your team’s next idea