Confluence Coding
You do confluence coding by using built-in page macros to format and display snippets. Teams also build custom scripts that read and write wiki pages through the platform API. Most teams set up shared spaces where engineers paste queries and scripts for daily tasks. When page roles are too broad, anyone can read secret keys pasted into those docs. How confluence coding works in team spaces Engineers use wiki pages to share SQL queries, shell scripts, and setup steps. The platform gives you a
Coding: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You do confluence coding by using built-in page macros to format and display snippets. Teams also build custom scripts that read and write wiki pages through the platform API. Most teams set up shared spaces where engineers paste queries and scripts for daily tasks. When page roles are too broad, anyone can read secret keys pasted into those docs.
How confluence coding works in team spaces
Engineers use wiki pages to share SQL queries, shell scripts, and setup steps. The platform gives you a built-in block macro to show text in a fixed font. This macro adds line numbers and color to make scripts easy to read. Authors pick a language from a list so the page highlights the right words.
Teams also write scripts that talk to the wiki API from outside tools. A build tool can send test logs to a page after every run.To do this, a user makes an API key tied to their own account. The script uses that key to log in and update the page text.
Some teams go further and build custom apps that run inside the wiki. These apps can pull live data from other tools and show it on a page. The wiki checks the user role before it loads the space or the page. If the user has read rights for that space, the page shows all its text.
What native page roles solve and what they miss
Space roles and page rules control who can open, edit, or delete a document. Admins can lock a space so only the engineering team can read the pages. They can also lock a single page so only leads can change the scripts on it. This setup stops guests from changing team docs by mistake.
Still, page roles only check who can open the document in the first place. They do not check what is inside the snippets or how people run them. Engineers often paste real database queries or shell commands straight from their work terminals. Those snippets often hold live keys, emails, phone numbers, or card numbers from past tests.
Coding: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Once a key or customer detail lands on a page, anyone with read rights sees it. Even worse, engineers copy these snippets and run them against live databases without a check. A wiki page cannot stop a user from running a bad query in production. It also cannot rewrite sensitive fields in the results that engineers copy back into docs.
Keeping keys and data safe during wiki workflows
Good wiki habits start with keeping live keys and real customer data out of docs. Teams should write sample queries with fake placeholders instead of real emails or national IDs. When scripts update wiki pages through the API, they should use scoped service accounts. Each service account should only have rights to the single space it needs to update.
Still, manual rules on a wiki page do not protect the live systems themselves. Teams need controls at the database and server level when engineers run shared snippets. Checking every command in flight stops bad edits before they hit the real data. Rewriting matched fields in query results also keeps raw data from ending up in wiki pages.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
How do you add a snippet to a wiki page?
Type the slash key in the editor and pick the block macro for snippets. Paste your text into the box and pick your language for color formatting.
Can you run scripts straight inside a wiki page?
No, standard wiki pages only display static text and do not run your scripts. You must copy the snippet to your own terminal or use an external build tool.
Why is pasting real query output into wiki pages risky?
Real query output often holds emails, phone numbers, card numbers, or live keys. Anyone who can read the wiki space will see that data in plain text.