> ## Documentation Index
> Fetch the complete documentation index at: https://docs.foundable.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Tools for your website
> Tools hold what runs behind your website: payments, its database, security and secret keys, GitHub, its AI and the emails it sends.
A website is more than its pages. Behind them are the parts that make it work: payments, a database, secret keys, AI, emails and more. **Tools**, in Build, is where you see and manage these parts, one website at a time.
Ted sets most of them up while he builds. You open Tools to see how things stand, change a setting, or do a job yourself.
Press **Build** in the top bar.
**Tools** sits at the top right of the board, and of every open website. It opens on the website you looked at last.
Choose one from the list on the left: **Payments**, **Database**, **Security**, **GitHub**, **AI** or **Emails**.
Each tool shows one website. To see another, press the website’s name at the top and pick it from the list.
To leave Tools, press the back arrow at the top left, or Escape.
## What each tool does
Take payments on your website and see your sales.
The information your website keeps, and the people who signed up.
Scan for leaked keys, and keep the secret keys your website uses.
Keep your website’s code in a GitHub repository you own.
See what your website’s AI answers and spends, and set a daily limit.
See the emails your website sends, and send yourself a test.
### Payments
With **Payments**, your website can sell. Setting it up starts with one press, then Stripe’s own pages ask for your business and bank details. Once Stripe approves them, Payments shows your sales. See [Get paid with Payments](/payments/overview).
### Your own domain
A [domain](/help/glossary#domain), like yourbusiness.com, isn’t one of the Tools. You buy one or connect one you already own in **Settings** › **Domains**, or from the **Domains** row of the Publish panel. See [Use your own domain](/domains/overview).
### Logs
**Logs** isn’t in the list. It opens when something goes wrong. If your website runs into an error in the preview, a card says “The website encountered an error”. Press **Show logs** on it to open **Server logs**.
Server logs list your website’s requests and errors, from its preview and its published site. They’re kept 7 days, and your [secrets](/build/security#secrets) show as `[secret NAME]`, never their values. In Server logs you can:
* Pick a time range, from **Last hour** to **Custom range…**
* Show only the **Errors**
* **Search events**
* Download them as a file (“Download logs as a JSON file”)
* Press **Try to fix** on an error to ask Ted to fix it
“No server logs yet” means your website hasn’t needed its server yet: “Requests and errors will appear here when your website uses server code.”
## Who sees which tool
Everyone in your foundable can open Tools. Some tools show only for some [roles](/account/team):
| Role | Tools they see |
| - | - |
| Owner and admin | All six. |
| Member | Every tool but **Emails**. |
| View only | **Payments**, **Database**, **Security** and **AI**. |
What someone can change inside a tool also depends on their role, and each tool’s page says who can do what. Where a teammate can’t make a change, the tool tells them who can, for example “Only the owner or an admin can add or change them.”
## When a tool has nothing to show
| What you see | What it means | What to do |
| - | - | - |
| “Loading your websites…” | Tools is finding your websites. | Wait a moment. |
| “Couldn’t load your websites” with “Trying again…” | Your websites didn’t load this time. | Wait. Tools tries again by itself. |
| “No website yet” | Your foundable has no website for this tool to show. | Ask Ted to build one. Each tool says what it will show, like “Build a website to keep its code in GitHub.” |
## Tools on a phone
On a phone, Tools opens as a list. Press a tool to open it, and press **Back to tools** to return to the list.
## Ted and your tools
Ted works with your tools too, so you rarely set things up by hand:
* Your website’s database is set up by itself when Build creates the website, and Ted changes its tables when your website needs it.
* When your website needs a key from another service, Ted asks you for it on a card, and it’s kept in Security’s **Secrets**.
* Ted can connect a website to GitHub from the chat.
* Ted can read your website’s AI usage and change its daily limit and model.
* Ted writes newsletters for your website’s subscribers. Each one waits for an owner’s or admin’s OK before it goes out.
## FAQ
Your role decides. **Emails** shows only for the owner and admins, because it shows who each email went to. **GitHub** shows for everyone but view-only teammates.
Logs opens from an error. When your website runs into one in the preview, press **Show logs** on the error card. See [Logs](#logs).
Every new website gets its database, on every plan. Your website’s AI is paid from your [credits](/help/glossary#credit), and shows as “Website AI” in your usage. Two things need a paid plan. One is sending your website’s emails to your customers: on Free, they go only to you. The other is **Download code** in the GitHub tool.
No. Foundable sends your website’s emails for you, and your website’s AI needs no key of its own. If you’d rather pay OpenAI yourself, you can add your own OpenAI key. See [Use your own OpenAI key](/build/website-ai#use-your-own-openai-key).
## Related
Your websites, the board and the preview.
See and change what your website keeps.
Scan your website and keep its keys safe.
Sell from your website.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.