How plugins work in Integrations
The Integrations page gathers the services your organization connects to Baila — today, the Asaas payment gateway — and the Payments page shows what is still missing.
Everything your organization connects to Baila lives in one place: Integrations, in the dashboard's sidebar. Each service is a plugin, with its own card and its own settings window. Today the available plugin is Asaas, the gateway that takes ticket payments straight into your own account (the BYOG model).
What the page shows
Cards are grouped by type — for example, Payment gateways. Each card shows where your organization stands:
| On the card | What it means |
|---|---|
| No badge and an Install button | The plugin is available and not set up yet. (The button only shows to people who can manage payments.) |
| Setup incomplete | A step is missing — open the plugin to see which one. |
| Ready to sell | You can publish paid events and bill your fan club. |
| Ready to sell and split revenue | On top of that, your payout account is verified: co-hosting is unlocked. |
| Coming soon | The plugin cannot be installed yet (PagSeguro and Redecard, for now). |
| Not available in your country | The plugin is not offered in your organization's country. |
At the top of the page you see your organization country. It decides which plugins are offered. To change it, contact support.
Further down, under Developers, people who can manage API keys find the shortcut to API keys and MCP.
The plugin window
Click Install or Configure to open the plugin's window. After the first save, its list of steps appears at the top, each with a status (Done, Pending or Needs attention) and what it unlocks. A step marked recommended blocks nothing, but is worth doing. Below it are the plugin's fields and sections. The Asaas walkthrough is in How to connect my Asaas payment gateway.
Your organization uses one payment gateway at a time. Keys and credentials are stored encrypted and never shown back: to change one, type the new one over it.
People without permission to manage payments (the manager role, for example) see the window read-only: they can check each step's status but cannot change anything.
The Payments page
Payments, also in the sidebar, is read-only: it sums up what your organization still needs to get paid for tickets, and what each step unlocks. Every pending step has a button that opens the plugin's window right on that step. When something blocks an action, Baila shows a link to this page — for example, publishing a paid event before Asaas is ready, or accepting a co-hosting invite without a verified payout account.
Related articles
How to change roles, remove people and transfer ownership
Edit the access of someone already on the team, build a custom role, take someone out of the organization, and hand ownership to another person.
How to create and manage API keys
Create a key so another tool can act on your organization, pick its access level, store the secret safely, and revoke it when you are done.