> ## Documentation Index
> Fetch the complete documentation index at: https://tbd-6fc993ce-hypeship-docs-ia-v2.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Overview

> Organize, secure, and govern how your team uses KERNEL

Management settings apply across your organization rather than to a single browser: how resources are split between teams and environments, who and what can call the API, what happened and when, and how much you spend.

<Columns className="responsive-columns" cols={3}>
  <Card title="Projects" icon="folder-tree" href="/info/projects">
    Separate environments, teams, or customers, each with its own browsers, profiles, credentials, and limits.
  </Card>

  <Card title="API keys" icon="key" href="/info/api-keys">
    Create, scope, rotate, and delete the keys your code and agents use.
  </Card>

  <Card title="Spending caps" icon="gauge" href="/info/spending-caps">
    Set a monthly spending guardrail for your organization, a project, or both.
  </Card>

  <Card title="Audit logs" icon="list-check" href="/info/audit-logs">
    A year of API request history across your organization, searchable and exportable on Start-Up and Enterprise.
  </Card>

  <Card title="Firewall allowlist" icon="network-wired" href="/info/network-access">
    The KERNEL domains and ports to allow if your firewall restricts outbound traffic.
  </Card>
</Columns>

## Multi-tenant setups

If you run KERNEL on behalf of your own customers, combine these pieces so each customer is isolated and capped:

* **One [project](/info/projects) per customer.** Each project has its own browsers, profiles, credentials, proxies, and deployments.
* **A [project-scoped API key](/info/api-keys) per customer workload.** A project-scoped key can only reach resources in its project.
* **A [spending cap](/info/spending-caps) and a [concurrency limit](/info/projects#concurrency-limits) per project.** One customer's usage can't exhaust your budget or your organization's browser limit.
* **One [profile](/browsers/profiles) per end user.** Each user's logins and browser state stay separate, inside their customer's project.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.