--- title: SalexHub documentation description: How SalexHub works, how to set up an organization, what the Agent may do on its own, and how to build on it. Each page is checked against the product's code. url: https://salexhub.com/docs --- # SalexHub documentation How the platform works, how to set it up, and how to build on it. Each page names where in the product's code it was checked. ## Get started What SalexHub is, and the first things to set up in an organization. - [What SalexHub is](https://salexhub.com/docs/get-started): One organization for the whole business: customers, sales, operations, your team's work and HR on the same records, with the Agent working on them. - [Set up your organization](https://salexhub.com/docs/get-started/set-up): From a new account to an organization your team can use: AI credits or a key before the Agent, the legal entity before the first invoice. - [Glossary](https://salexhub.com/docs/glossary): The words the SalexHub documentation uses, each in one sentence, with the page that explains it. ## The Agent The key it runs on, what it may do on its own, what always waits for a person, and working from the chat. - [Connect an AI provider](https://salexhub.com/docs/agent/ai-provider): The Agent runs on paid AI credits or your own AI provider key: which providers work, how to add a key, which models it opens, and what it spends. - [Autonomy and approvals](https://salexhub.com/docs/agent/autonomy): How much the Agent may do without asking, who decides that, and what waits for a person whatever the setting. - [Work from the chat](https://salexhub.com/docs/agent/chat): The second way to work: tell the Agent what you need at chat.salexhub.com. How it differs from the app, what stays in the app, and what a visitor gets. ## Control & audit Roles, who sees which records and values, approval rules, and the audit log. - [Roles and permissions](https://salexhub.com/docs/control/roles): The seven built-in roles, the twelve rights a role can hold, custom roles, and how people join, change role and leave an organization. - [Access and sharing](https://salexhub.com/docs/control/access): Which records a person sees beyond their own: access defaults, teams, sharing and restriction rules, sharing by hand, and field access per property. - [Teams](https://salexhub.com/docs/control/teams): A hierarchy of teams that decides whose records a person sees, who is in each team, and, on Enterprise, which roles a team gives to its members. - [Approval rules](https://salexhub.com/docs/control/approval-rules): Acts that wait for someone's yes before they happen: what a rule can hold, who decides and in what order, and what happens after the last yes. - [Audit log](https://salexhub.com/docs/control/audit-log): Who did what in the organization, from where and when, including what was refused. What is recorded, what your plan lets you read, and how to export it. ## Plans & usage The plan an organization runs on, what it uses, AI credits, the products it switches on, and its invoices. - [Plans, trial and seats](https://salexhub.com/docs/billing/plans): The plan an organization runs on, its trial and seats, how a plan is bought, who may change it, and what the Billing screen refuses. - [Usage](https://salexhub.com/docs/billing/usage): What the organization uses of what its plan includes, how close each figure is to its limit, and what happens at a limit. - [AI credits](https://salexhub.com/docs/billing/ai-credits): Where AI credits come from and when they expire, what spends them, how to read Budgets & Spend, how to buy a pack, and what happens at zero. - [Products](https://salexhub.com/docs/billing/products): The Products screen lists the products an organization can switch on or off for everyone, says why one cannot be switched on, and what switching one off keeps. - [Invoices and payment](https://salexhub.com/docs/billing/invoices): Where invoices are listed, how to view, download and pay one, where cards and invoice details are kept, and what the page refuses. ## Files & storage Where files live, what counts toward the plan's storage, and the recycle bin. - [Files and storage](https://salexhub.com/docs/storage/files): How much file storage the organization uses against its plan, what counts toward it, what happens when it is full, and how to find a file. ## Developers The API and the MCP server, webhooks, embeds, the form endpoint, the tracking script and the messenger bridge. - [Build on SalexHub](https://salexhub.com/docs/developers): The REST API and the MCP server on one registry of tools, webhooks, embeds, forms, tracking and a messenger bridge: what a developer can connect today. - [Webhooks](https://salexhub.com/docs/developers/webhooks): Signed HTTPS deliveries when a record is created or updated or a document moves, with retries, a delivery log and a verification routine to copy. - [Embeds](https://salexhub.com/docs/developers/embeds): Live data from records you publish, on a site SalexHub does not host: a script tag, or JSON and HTML from one address. Read-only, keyless, no personal data. - [Form endpoint](https://salexhub.com/docs/developers/forms): Send your site's form to your organization. Each submission with an email or a phone is stored, matched to a contact or turned into one, and can open a deal. - [Tracking script](https://salexhub.com/docs/developers/tracking): One script tag for cookie-free web analytics: page views, your own events, and identifying a visitor who gives an email. What it collects and never stores. - [Messenger bridge](https://salexhub.com/docs/developers/messenger-bridge): Bring a messenger's conversations into your organization through a bridge you run. Messages arrive with a channel key; replies go back by signed push or pull. - [API keys, REST and MCP](https://salexhub.com/docs/developers/api-keys): How to issue an API key, what it may do, and how to call the REST API and the MCP server with it. The TypeScript SDK is not published yet. --- The same page for people: https://salexhub.com/docs. Index of this site for agents: https://salexhub.com/llms.txt